Difference between revisions of "Documentation/Nightly/Developers/Tutorials/ContributePatch"
m |
m |
||
| Line 10: | Line 10: | ||
<li><p>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]</p></li> | <li><p>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]</p></li> | ||
| − | <li><p>Make sure your | + | <li><p>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.</p> |
<pre> | <pre> | ||
git remote add jcfr git@github.com:jcfr/Slicer.git | git remote add jcfr git@github.com:jcfr/Slicer.git | ||
Revision as of 15:49, 16 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 here.
Create an issue in the tracker. For example, see issue #1906
Make sure your clone has a git remote. After forking Slicer repository, replace
jcfrwith your git login.git remote add jcfr git@github.com:jcfr/Slicer.git
Create a topic named
<issuer_number>-a-descriptive-topic-name. For example:git checkout -b 1906-uninstall-extensions-on-restart
-
Fix the code or implement your feature, then commit your change(s)
- Make sure to read the Slicer Coding and Commit Style Guide
Publish the topic on your fork
git push jcfr 1906-uninstall-extensions-on-restart
Add a note to the issue with a link pointing to your topic. For example, see note 1906#c4578
