UpdateBot: Nightly -> 4.5

2015-11-12T21:54:06Z

Nightly -> 4.5

New page

<noinclude>{{documentation/versioncheck}}</noinclude>
The following instructions describes the recommended workflow to contribute patch to Slicer code base.

It is assumed that you followed the [[Documentation/Nightly/Developers/StartHere#New_community_member_checklist|New community member checklist]], have a clone of https://github.com/Slicer/Slicer/ and have setup the development environment as described [[Documentation/Nightly/Developers/DevelopmentWithGit#Slicer_Setup | here]].

<ol start="1" style="list-style-type: decimal;">

<li>Create an issue in the [http://na-mic.org/Mantis/bug_report_page.php tracker]. For example, see issue [http://na-mic.org/Mantis/view.php?id=1906 #1906]</li>

<li>Make sure your clone has a [https://help.github.com/articles/adding-a-remote git remote]. After [https://help.github.com/articles/fork-a-repo forking Slicer repository], replace <code>jcfr</code> with your git login.
<pre>
git remote add jcfr git@github.com:jcfr/Slicer.git
</pre>
</li>

<li>Create a topic named <code><issuer_number>-a-descriptive-topic-name</code>. For example:
<pre>
git checkout -b 1906-uninstall-extensions-on-restart
</pre>
</li>

<li>
Fix the code or implement your feature, then commit your change(s)
<ol style="list-style-type:none; border-left:thick solid red; padding-left:1em;">
<li>Make sure to read the [[Documentation/{{documentation/version}}/Developers/Style_Guide|Slicer Coding and Commit Style Guide]] </li>
</ol>
</li>

<li>Publish the topic on your fork
<pre>
git push jcfr 1906-uninstall-extensions-on-restart
</pre>
</li>

<li>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]</li>



</ol>

Documentation/4.5/Developers/Tutorials/ContributePatch - Revision history

UpdateBot: Nightly -> 4.5