1
- Please make sure you have read the PR guidelines below, and checked all boxes that apply at the bottom.
2
-
3
1
## Changes proposed in this pull request
4
2
5
- ** Please describe here the main features / changes proposed for review and integration in fMRIPrep**
6
-
7
- If this PR addresses some existing problem, please use GitHub's citing tools (eg. `` ref # `` , `` closes # `` or `` fixes # `` ).
3
+ <!--
4
+ Please describe here the main features / changes proposed for review and integration in fMRIPrep
5
+ If this PR addresses some existing problem, please use GitHub's citing tools
6
+ (eg. ref #, closes # or fixes #).
8
7
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).
8
+ issue first and then link it from here (so the *fMRIPrep* community has a better understanding
9
+ of ongoing development efforts and possible overlaps between contributions).
10
+ -->
11
11
12
12
13
13
## Documentation that should be reviewed
14
-
15
- Please summarize the main changes to the documentation that the reviewers should be aware of.
14
+ <!--
15
+ Please summarize here the main changes to the documentation that the reviewers should be aware of.
16
+ -->
16
17
17
18
## Pull-request guidelines:
18
-
19
+ <!--
20
+ Please make sure you have read the PR guidelines below, and checked
21
+ all boxes that apply at the bottom.
22
+ -->
19
23
1 . We invite you to list yourself as a * fMRIPrep* contributor, so if your name
20
24
is not already mentioned, please modify the
21
25
[ `` .zenodo.json `` ] ( https://github.com/poldracklab/fmriprep/blob/master/.zenodo.json )
@@ -36,21 +40,23 @@ Please summarize the main changes to the documentation that the reviewers should
36
40
2 . By submitting this request you acknowledge that your contributions are available under the BSD 3-Clause license.
37
41
38
42
3 . Use a descriptive prefix, between brackets for your PR: `` ENH `` (enhancement), `` FIX `` , `` TST `` , `` DOC `` , `` STY `` ,
39
- `` REF `` (refactor), `` WIP `` (Work in progress ), `` MAINT `` (maintenance). Example:
43
+ `` REF `` (refactor), `` CI `` (continous integration ), `` MAINT `` (maintenance). Example:
40
44
```
41
45
[ENH] Support for SB-reference in multi-band datasets
42
46
```
47
+ For works-in-progress, add the `` WIP `` tag in addition to the descriptive prefix.
43
48
Pull-requests tagged with `` [WIP] `` will not merged in until the tag is removed.
44
49
45
- 4 . Your PR will be reviewed following the following
50
+ 4 . Your PR will be reviewed according to the following
46
51
[ template] ( https://github.com/poldracklab/fmriprep/wiki/Reviewing-a-Pull-Request ) .
47
52
48
53
5 . Documentation is a fundamental aspect to the * glass-box* philosophy that * fMRIPrep* abides by.
49
54
Please understand that the * fMRIPrep* team may (are likely to) request you to improve the documentation
50
55
provided with this PR, within the PR or in future PRs.
51
56
52
57
53
- ** Please check what corresponds** :
58
+ ** Please review and check the following** :
59
+ <!-- replace the empty checkboxes [ ] below with checked ones [x] accordingly -->
54
60
55
61
- [ ] I have read the [ guidelines for contributions] ( https://github.com/poldracklab/fmriprep/blob/master/CONTRIBUTING.md ) .
56
62
- [ ] I understand that my contributions will not be merged unless the work is
0 commit comments