You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/PULL_REQUEST_TEMPLATE.md
+4-3
Original file line number
Diff line number
Diff line change
@@ -4,8 +4,9 @@ Developers are strongly encouraged to first make a PR to their own plotly.js for
4
4
5
5
Before opening a pull request, developer should:
6
6
7
-
-`git rebase` their local branch off the latest `master`
8
-
- make sure to **not**`git add` the `dist/` folder (the `dist/` is updated only on verion bumps)
9
-
- write an overview of what the PR attempts to do.
7
+
-`git rebase` their local branch off the latest `master`,
8
+
- make sure to **not**`git add` the `dist/` folder (the `dist/` is updated only on verion bumps),
9
+
- write an overview of what the PR attempts to do,
10
+
- select the _Allow edits from maintainers_ option (see this [article](https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) for more details).
10
11
11
12
Note that it is forbidden to force push (i.e. `git push -f`) to remote branches associated with opened pull requests. Force pushes make it hard for maintainers to keep track of updates. Therefore, if required, please `git merge master` into your PR branch instead of `git rebase master`.
0 commit comments