blob: 1730a08f7cafa8eea06003d3528521cfd50c45db (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
|
<!--
Thank you for submitting a PR to pylint!
To ease the process of reviewing your PR, do make sure to complete the following boxes.
- [ ] 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``
-->
## Type of Changes
<!-- Leave the corresponding lines for the applicable type of change: -->
| | Type |
| --- | ---------------------- |
| ✓ | :bug: Bug fix |
| ✓ | :sparkles: New feature |
| ✓ | :hammer: Refactoring |
| ✓ | :scroll: Docs |
## Description
<!-- If this PR references an issue without fixing it: -->
Refs #XXXX
<!-- If this PR fixes an issue, use the following to automatically close when we merge: -->
Closes #XXXX
|
