@@ -5,7 +5,9 @@ Please make sure you have read the PR guidelines below, and checked all boxes th
5
5
** Please describe here the main features / changes proposed for review and integration in fMRIPrep**
6
6
7
7
If this PR addresses some existing problem, please use GitHub's citing tools (eg. `` ref # `` , `` closes # `` or `` fixes # `` ).
8
-
8
+ If there is not an existing issue open describing the problem, please consider opening a new
9
+ issue first and then link it from here (so the * fMRIPrep* has a better understanding of ongoing development
10
+ efforts and possible overlaps between contributions).
9
11
10
12
11
13
## Documentation that should be reviewed
@@ -50,10 +52,10 @@ Please summarize the main changes to the documentation that the reviewers should
50
52
51
53
** Please check what corresponds** :
52
54
53
- - [ ] I have read the [ community rules for contributions] ( https://github.com/poldracklab/fmriprep/blob/master/CONTRIBUTING.md ) .
55
+ - [ ] I have read the [ guidelines for contributions] ( https://github.com/poldracklab/fmriprep/blob/master/CONTRIBUTING.md ) .
54
56
- [ ] I understand that my contributions will not be merged unless the work is
55
57
finished (i.e. no `` [WIP] `` tag remains in the title of my PR) and tests pass.
56
58
- [ ] The proposed code follows the
57
- [ coding guidelines ] ( https://github.com/poldracklab/fmriprep/blob/master/CONTRIBUTING.md#fmriprep-coding-style-guide ) ,
59
+ [ coding style ] ( https://github.com/poldracklab/fmriprep/blob/master/CONTRIBUTING.md#fmriprep-coding-style-guide ) ,
58
60
to the extent I understood them (and I will address any comments raised by the PR's reviewers in this regard).
59
61
- [ ] \( Optional\) I opt-out from being listed in the ` .zenodo.json ` file.
0 commit comments