Difference between revisions of "Documentation/4.1/Developers/Tutorials/ContributePatch"
From Slicer Wiki
m |
|||
| Line 1: | Line 1: | ||
<noinclude>{{documentation/versioncheck}}</noinclude> | <noinclude>{{documentation/versioncheck}}</noinclude> | ||
| − | here | + | here {{documentation|isdevelopers}} here |
The following instructions describes the recommended workflow to contribute patch to Slicer code base. | The following instructions describes the recommended workflow to contribute patch to Slicer code base. | ||
Revision as of 05:59, 14 June 2013
Home < Documentation < 4.1 < Developers < Tutorials < ContributePatch
|
For the latest Slicer documentation, visit the read-the-docs. |
here
[create] Documentation
here
The following instructions describes the recommended workflow to contribute patch to Slicer code base.
It is also assumed you followed the New community member checklist and have a clone of https://github.com/Slicer/Slicer/.
- 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. Add a note to the issue with a link pointing to your topic. For example, see note 1906#c4578
- 5. Send an email on the slicer-developers list pointing to the reported bug. Title of the email should start with
[BUG <IssueNumber>] Title of the bug - <category>
