diff options
| author | Pierre Sassoulas <pierre.sassoulas@gmail.com> | 2023-02-23 23:33:04 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-02-23 22:33:04 +0000 |
| commit | c4f059bd08731cd468de712725c9cb0ecfd4e824 (patch) | |
| tree | 04c422d34bb9a4ba683c3ea924941a9da95eccde /.github | |
| parent | 8f24c69d3f6f9ff19d4b867c840bc1dd560ddddb (diff) | |
| download | pylint-git-c4f059bd08731cd468de712725c9cb0ecfd4e824.tar.gz | |
[PR documentation] Add advice to keep the pull requests small (#8330)
Co-authored-by: Daniël van Noord <13665637+DanielNoord@users.noreply.github.com>
Diffstat (limited to '.github')
| -rw-r--r-- | .github/PULL_REQUEST_TEMPLATE.md | 17 |
1 files changed, 12 insertions, 5 deletions
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md index dfa06dbbb..1730a08f7 100644 --- a/.github/PULL_REQUEST_TEMPLATE.md +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -3,11 +3,18 @@ Thank you for submitting a PR to pylint! To ease the process of reviewing your PR, do make sure to complete the following boxes. -- [ ] Write a good description on what the PR does. -- [ ] Create a news fragment with `towncrier create <IssueNumber>.<type>` which will be - included in the changelog. `<type>` can be one of: breaking, user_action, feature, - new_check, removed_check, extension, false_positive, false_negative, bugfix, other, internal. - If necessary you can write details or offer examples on how the new change is supposed to work. +- [ ] Document your change, if it is a non-trivial one. + - A maintainer might label the issue ``skip-news`` if the change does not need to be in the changelog. + - Otherwise, create a news fragment with ``towncrier create <IssueNumber>.<type>`` which will be + included in the changelog. ``<type>`` can be one of the types defined in `./towncrier.toml`. + If necessary you can write details or offer examples on how the new change is supposed to work. + - Generating the doc is done with ``tox -e docs`` +- [ ] Relate your change to an issue in the tracker if such an issue exists (Refs #1234, Closes #1234) +- [ ] Write comprehensive commit messages and/or a good description of what the PR does. +- [ ] Keep the change small, separate the consensual changes from the opinionated one. + Don't hesitate to open multiple PRs if the change requires it. If your review is so + big it requires to actually plan and allocate time to review, it's more likely + that it's going to go stale. - [ ] If you used multiple emails or multiple names when contributing, add your mails and preferred name in ``script/.contributors_aliases.json`` --> |