File tree Expand file tree Collapse file tree 1 file changed +4
-1
lines changed Expand file tree Collapse file tree 1 file changed +4
-1
lines changed Original file line number Diff line number Diff line change @@ -220,6 +220,9 @@ but those accepted fastest will follow a workflow similar to the following:
220
220
using a [ NiPreps development environment] [ link_devel ] .
221
221
Once you are satisfied with your local changes, [ add/commit/push them] [ link_add_commit_push ]
222
222
to the branch on your forked repository.
223
+ Note that that each commit must include changes that serve a coherent
224
+ purpose only (e.g. documentation, feature, bug fix) and that have a clear
225
+ scoped. They should be prefixed as indicated below.
223
226
224
227
1 . ** Submit a [ pull request] [ link_pullrequest ] .** <br />
225
228
A member of the development team will review your changes to confirm
@@ -233,7 +236,7 @@ but those accepted fastest will follow a workflow similar to the following:
233
236
* ` STY ` : style changes ([ example] [ sty_ex ] )
234
237
* ` REF ` : refactoring existing code ([ example] [ ref_ex ] )
235
238
* ` CI ` : updates to continuous integration infrastructure ([ example] [ ci_ex ] )
236
- * ` MAINT ` : general maintenance ([ example] [ maint_ex ] )
239
+ * ` MAINT ` / ` MNT ` : general maintenance ([ example] [ maint_ex ] )
237
240
* For works-in-progress, add the ` WIP ` tag in addition to the descriptive prefix.
238
241
Pull-requests tagged with ` WIP: ` will not be merged until the tag is removed.
239
242
You can’t perform that action at this time.
0 commit comments