Update docs to reflect this change

Author: camdecoster

.github/PULL_REQUEST_TEMPLATE.md

@@ -18,5 +18,5 @@ Before opening a pull request, developer should:
 7. 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).
 
 After opening a pull request, developer:
- - should create a new small markdown log file using the PR number e.g. `1010_fix.md` or `1010_add.md` inside `draftlogs` folder as described in this [README](https://github.com/plotly/plotly.js/blob/master/draftlogs/README.md), commit it and push.
+ - should create a new small markdown log file using the PR number e.g. `1010_fix.md` or `1010_add.md` inside `draftlogs` folder as described in this [README](https://github.com/plotly/plotly.js/blob/master/draftlogs/README.md), commit it and push. A CI check enforces this; PRs that don't warrant a CHANGELOG entry can opt out by applying the `no-draftlog` label.
  - should **not** 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 fetch `upstream/master` and "merge" with master instead of "rebase".

CONTRIBUTING.md

@@ -71,6 +71,7 @@ We use the following [labels](https://github.com/plotly/plotly.js/labels) to tra
 | `status: in progress` | PRs that required some initial feedback but not ready to merge |
 | `status: reviewable` | PRs that are completed from the author's perspective |
 | `status: on hold` | PRs that are put on hold |
+| `no-draftlog` | PR opted out of the [draftlog](./draftlogs/README.md) check |
 
 ## Development
 

draftlogs/README.md

@@ -19,4 +19,15 @@ If your PR falls into more than one category - for example adding a new feature
 which would render
  - Add `icicle` trace type [[#5546](https://github.com/plotly/plotly.js/pull/5546)]
 
-> Please start your single-line or multiple lined message with a verb. You could basically use the PR description while providing a link to the PR similar to the above example is appreciated too.
+> Please start your single-line or multiple lined message with a verb.
+
+Each entry must include a link back to the PR in the form shown above:
+`[[#1234](https://github.com/plotly/plotly.js/pull/1234)]` (a link to
+`/issues/1234` is also accepted, since GitHub redirects between the two).
+
+### Skipping the draftlog
+
+A CI check enforces that every pull request adds a new file under
+`draftlogs/`. If your PR genuinely does not warrant a CHANGELOG entry
+(e.g. a CI-only change, internal refactor, or docs typo), add the
+`no-draftlog` label to the PR to opt out.