Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit d58a7b5

Browse filesBrowse files
committed
add info about 'Allow edits from maintainers' option in PR template
1 parent 3ebe797 commit d58a7b5
Copy full SHA for d58a7b5

File tree

1 file changed

+4
-3
lines changed
Filter options

1 file changed

+4
-3
lines changed

‎.github/PULL_REQUEST_TEMPLATE.md

Copy file name to clipboardExpand all lines: .github/PULL_REQUEST_TEMPLATE.md
+4-3Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,9 @@ Developers are strongly encouraged to first make a PR to their own plotly.js for
44

55
Before opening a pull request, developer should:
66

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).
1011

1112
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

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.