Difference between revisions of "Documentation/Nightly/Developers/Tutorials/ContributePatch"
From Slicer Wiki
m |
m |
||
| Line 18: | Line 18: | ||
</pre> | </pre> | ||
| − | * 4. | + | * 4. Hack, hack, hack and commit your change |
| − | * 5. Send an email on the [http://massmail.bwh.harvard.edu/mailman/listinfo/slicer-devel slicer-developers] list pointing to the reported bug. Title of the email should start with <code>[BUG <IssueNumber>] Title of the bug - <category></code> | + | * 5. Publish the topic on your fork |
| + | <pre> | ||
| + | git push jcfr 1906-uninstall-extensions-on-restart | ||
| + | </pre> | ||
| + | |||
| + | * 6. Add a note to the issue with a link pointing to your topic. For example, see note [http://na-mic.org/Mantis/view.php?id=1906#c4578 1906#c4578] | ||
| + | |||
| + | <!-- | ||
| + | * 7. Send an email on the [http://massmail.bwh.harvard.edu/mailman/listinfo/slicer-devel slicer-developers] list pointing to the reported bug. Title of the email should start with <code>[BUG <IssueNumber>] Title of the bug - <category></code> | ||
| + | --> | ||
Revision as of 17:59, 9 July 2013
Home < Documentation < Nightly < Developers < Tutorials < ContributePatch
|
For the latest Slicer documentation, visit the read-the-docs. |
The following instructions describes the recommended workflow to contribute patch to Slicer code base.
It is assumed that you followed the New community member checklist, have a clone of https://github.com/Slicer/Slicer/ and have setup the development environment as described in the here.
If not already done, make sure to read the Slicer Coding Style Guide :-)
- 2. Make sure your fork has a git remote. Replace
jcfrwith your git login.
git remote add jcfr git@github.com:jcfr/Slicer.git
- 3. Create a topic named
<issuer_number>-a-descriptive-topic-name. For example:
git checkout -b 1906-uninstall-extensions-on-restart
- 4. Hack, hack, hack and commit your change
- 5. Publish the topic on your fork
git push jcfr 1906-uninstall-extensions-on-restart
- 6. Add a note to the issue with a link pointing to your topic. For example, see note 1906#c4578
