chore(github): replace develop branch with master (#147)

A few people has been confused by this already.
visjs · Oct 2, 2019 · edc9995 · edc9995
1 parent 1a03631
commit edc9995
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
@@ -2,8 +2,8 @@
 
 Please make sure to check the following requirements before creating a pull request:
 
-* [ ] All pull requests must be to the [develop branch](https://github.com/almende/vis/tree/develop). Pull requests to the `master` branch will be closed!
-* [ ] Make sure your changes are based on the latest version of the [develop branch](https://github.com/almende/vis/tree/develop). (Use e.g. `git fetch && git rebase origin develop` to update your feature branch).
+* [ ] All pull requests must be to the [master branch](https://github.com/visjs/vis-network). Pull requests to any other branch will be closed!
+* [ ] Make sure your changes are based on the latest version of the [master branch](https://github.com/visjs/vis-network). (Use e.g. `git fetch && git rebase origin master` to update your feature branch).
 * [ ] Provide an additional or update an example to demonstrate your changes or new features.
 * [ ] Update the documentation if you introduced new behavior or changed existing behavior.
 * [ ] Reference issue numbers of issues that your pull request addresses. (If you write something like `fixes #1781` in your git commit message this issue gets closed automatically by merging your pull request).