Patch & Commit

Submit Patches

The first few times you make changes to the manual, you will need to submit them as patches for an administrator to review. This is just to make sure that we maintain a quality user manual, and that you do not accidentally break anything vital before you get used to the system.

In order to submit a patch, follow this process:

Make any changes that you want.
Create a patch file by running:
```
svn diff > filename.diff
```
This creates a simple text file that shows what text was added, removed or changed between your working files and the central repository.

If you have created or deleted files, you will need to run svn add /path/to/file or svn rm /path/to/file before creating the diff. To see a list of affected files, run svn status.
Upload the diff file here. If you do not have an account already, you can register for one.
After submitting the diff, you will be asked to « Create a new Revision » before you can add a title and description of your changes.
Please check if the Documentation project is assigned in the tag’s field in order to notify the team of your patch. You can also contact the team over the mailing list or Blender Chat.
They will review your patch and let you know about any changes you could make. If there is no issue, your patch will be accepted and then committed by the team of your patch.

Note

If your patch includes changes to or additional images, simply attach them when you are creating the revision.

Straightforward patches are bound to be accepted very quickly. Once you get accustomed to making changes and no longer need feedback, we cut out the middle man and give you direct access to edit the manual.

Voir aussi

See Release Cycle for documentation on how to make commits to a specific release branch and how to create merge commits.

Commit Directly

Once you are provided with the direct access to edit the manual, you can start committing directly instead of creating a patch file. Doing this will submit the change directly to our central repository.

All you need to do now is run:

svn commit -m "This is what I did"

Si vous oubliez -m 'message', il vous sera demandé de taper un message dans un éditeur de texte.

Do not forget to always run svn update before committing.

Then you will be asked for your username and password (from developer.blender.org) before the change is committed.

Note

Make sure to use your username (case sensitive) and not your email.

Your modified files are uploaded to the central repository for others to work with and continue collaborating. Commits are tracked in the repositories Diffusion. Soon after your changes become visible in the online manual.

Écrire un bon message Commit

Lorsque vous apportez des modifications au manuel qui se rapportent directement à un commit spécifique (changement) dans Blender, il est utile de faire en sorte que le titre du commit soit le même que celui du commit fait dans Blender. Il est demandé d’inclure le hachage de validation de la validation effectuée dans le code source de Blender.

Par exemple, le commit rBM8473 inclut un descriptif indicatif des modifications apportées avec le hachage rBa71d2b260170. Le hachage peut être extrait de l’URL fournie dans la tâche de documentation pour une prochaine version spécifique.

D’autres modifications plus générales n’ont pas à suivre la politique ci-dessus, cependant, il est toujours important de clarifier la description des modifications que vous avez apportées et pourquoi. Il peut être utile de préfixer le titre du commit avec un mot de préfixe tel que Cleanup:` ou Fix:` lorsque vous effectuez respectivement des nettoyages ou des correctifs généraux.

La rédaction de bons messages de validation aide les administrateurs à suivre les modifications apportées et garantit que toutes les nouvelles fonctionnalités sont correctement documentées.