Difference between revisions of "Documentation/4.1/Developers/Tutorials/ContributePatch"
From Slicer Wiki
m |
m |
||
Line 1: | Line 1: | ||
<br> | <br> | ||
− | The following instructions describes | + | The following instructions describes the recommended workflow to contribute patch to Slicer code base. |
+ | |||
+ | It is also assumed you followed the [[Documentation/4.1/Developers/StartHere#New_community_member_checklist|New community member checklist]] and have a clone of https://github.com/Slicer/Slicer/. | ||
Revision as of 16:42, 20 June 2012
Home < Documentation < 4.1 < Developers < Tutorials < ContributePatch
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 is a git remote. Replace
jcfr
with 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.