aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorSam Potts <sam@potts.es>2021-01-29 23:15:44 +1100
committerGitHub <noreply@github.com>2021-01-29 23:15:44 +1100
commitea87b9c7884c53c97854fe3efc47528896cdde2b (patch)
tree00b1dc911333debd97dddef85ca38bebabd311ea
parentaa3378fd7303c42059728155719ff57952bb0fcc (diff)
downloadplyr-ea87b9c7884c53c97854fe3efc47528896cdde2b.tar.lz
plyr-ea87b9c7884c53c97854fe3efc47528896cdde2b.tar.xz
plyr-ea87b9c7884c53c97854fe3efc47528896cdde2b.zip
Update CONTRIBUTING.md
-rw-r--r--CONTRIBUTING.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 2b3efe9c..e140371e 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -49,6 +49,6 @@ So that you can start straight away.
- If your modifications changes the documented behavior or add new features, document these changes in [README.md](README.md).
-- When finished, push the changes to your GitHub repository and send a pull request to **develop**. Describe what your PR does.
+- When finished, push the changes to your GitHub repository and send a pull request. Describe what your PR does.
- If the Travis build fails, or if you get a code review with change requests, you can fix these by pushing new or rebased commits to the branch.