Difference between revisions of "Documentation/4.1/Developers/Tutorials/ContributePatch"

From Slicer Wiki
Jump to: navigation, search
m
Line 1: Line 1:
 
<br>
 
<br>
Assuming you followed the [[Documentation/4.1/Developers/StartHere#New_community_member_checklist|New community member checklist]], you should have a clone of https://github.com/Slicer/Slicer/.
+
 
 +
The following instructions describes what should be 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:41, 20 June 2012

Home < Documentation < 4.1 < Developers < Tutorials < ContributePatch


The following instructions describes what should be 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/.


  • 1. Create an issue in the tracker. For example, see issue #1906
  • 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