Skip to content

Commit f5ed23c

Browse files
committed
adding links
1 parent 595a70d commit f5ed23c

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

CONTRIBUTING.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -67,15 +67,17 @@ check out the [guide for adding new interfaces to Nipype][link_new_interfaces].
6767
When you are working on your changes, you should test frequently if you are not breaking the existing code,
6868
more on testing you will find [the testing section of Nipype documentation](http://nipype.readthedocs.io/en/latest/devel/testing_nipype.html).
6969

70-
It's a good practice to create a new branch of your Nipype repository for a new set of changes.
71-
7270
Before pushing your changes to GitHub run `make check-before-commit`, this will remove trailing spaces, create new auto tests,
7371
test entire package and build the documentation.
7472
If you get no errors, you're ready to submit your changes!
7573

74+
It's a good practice to create [a new branch](https://help.github.com/articles/about-branches/)
75+
of the repository for a new set of changes.
76+
77+
7678
**4. Submit a [pull request][link_pullrequest].**
7779

78-
A new pull request for your changes should be created from your GitHub account.
80+
A new pull request for your changes should be [created from your GitHub account](https://help.github.com/articles/creating-a-pull-request-from-a-fork/).
7981

8082
When opening a pull request, please use one of the following prefixes:
8183

0 commit comments

Comments
 (0)