aboutsummaryrefslogtreecommitdiff
path: root/CONTRIBUTING.md
diff options
context:
space:
mode:
authorMilan Curcic <caomaco@gmail.com>2020-09-07 12:18:51 -0400
committerGitHub <noreply@github.com>2020-09-07 12:18:51 -0400
commit20c37324fa7ed6ef65392704b577ba2f77fecae8 (patch)
tree0749985ae3482b1362749aee858f0cb61b42a366 /CONTRIBUTING.md
parent900e439be00e31d77e1e9e4fd929c589ebfcb417 (diff)
downloadfpm-20c37324fa7ed6ef65392704b577ba2f77fecae8.tar.gz
fpm-20c37324fa7ed6ef65392704b577ba2f77fecae8.zip
Update CONTRIBUTING.md
Co-authored-by: Laurence Kedward <laurence.kedward@bristol.ac.uk>
Diffstat (limited to 'CONTRIBUTING.md')
-rw-r--r--CONTRIBUTING.md5
1 files changed, 4 insertions, 1 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index abce974..690fa23 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -83,7 +83,10 @@ This is the workflow that we follow:
At this stage, the scope of the fix/feature, its behavior, and API if
applicable should be defined.
Only when you have community concensus on these items you should proceed
- to step 3.
+ to writing code and opening a PR.
+ __When actively working on code towards a PR, please assign yourself to the issue on github.__
+ This is good collaborative practice to avoid duplicated effort and also inform others what you
+ are currently working on.
3. Open a new Pull Request (PR) with your contribution.
The body of the PR should at least include a bullet-point summary of the
changes, and a detailed description is encouraged.