| 1 | **Cross-references to related issues.** If there is no existing issue that describes your bug or feature request, then [create an issue](https://github.com/cytoscape/cytoscape.js/issues/new/choose) before making your pull request.
|
| 2 |
|
| 3 | Associated issues: #X, #Y, #Z
|
| 4 |
|
| 5 | **Notes re. the content of the pull request.** Give context to reviewers or serve as a general record of the changes made. Add a screenshot or video to demonstrate your new feature, if possible.
|
| 6 |
|
| 7 | - This PR adds this.
|
| 8 | - This PR does that.
|
| 9 | - This PR allows us to do some other thing.
|
| 10 |
|
| 11 | **Checklist**
|
| 12 |
|
| 13 | Author:
|
| 14 |
|
| 15 | - [ ] The proper base branch has been selected. New features go on `unstable`. Bug-fix patches can go on either `unstable` or `master`.
|
| 16 | - [ ] Automated tests have been included in this pull request, if possible, for the new feature(s) or bug fix. Check this box if tests are not pragmatically possible (e.g. rendering features could include screenshots or videos instead of automated tests).
|
| 17 | - [ ] The associated GitHub issues are included (above).
|
| 18 | - [ ] Notes have been included (above).
|
| 19 |
|
| 20 | Reviewers:
|
| 21 |
|
| 22 | - [ ] All automated checks are passing (green check next to latest commit).
|
| 23 | - [ ] At least one reviewer has signed off on the pull request.
|
| 24 | - [ ] Just after this pull request is merged, it should be applied to both the `master` branch and the `unstable` branch. Normally, this just requires cherry-picking the corresponding merge commit from `master` to `unstable` -- or vice versa.
|