I've noticed that the current format of Pull Requests (PRs) lacks consistency, causing some inconvenience during collaboration and code reviews.
In light of this, I suggest adding a PR template to ensure a standardized format for PR submissions.
PR Template Suggest
# Description
<!-- Please include a summary of the changes and the related issue. -->
Closes # (issue)
## Type of change
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
- [ ] This change requires a documentation update
# Checklist:
- [ ] Lint code (using flake8)
- [ ] Run unit tests (`pytest`)
- [ ] Run unit and functional tests (`pytest --enable-functional`) (not required)
Please comment if there is anything else to modify or add.
The output of thefuck --version (something like The Fuck 3.1 using Python 3.5.0 and Bash 4.4.12(1)-release):
n/a
Your system (Debian 7, ArchLinux, Windows, etc.):
n/a
How to reproduce the bug:
n/a
The output of The Fuck with THEFUCK_DEBUG=true exported (typically execute export THEFUCK_DEBUG=true in your shell before The Fuck):
n/a
If the bug only appears with a specific application, the output of that application and its version:
I've noticed that the current format of Pull Requests (PRs) lacks consistency, causing some inconvenience during collaboration and code reviews. In light of this, I suggest adding a PR template to ensure a standardized format for PR submissions.
PR Template Suggest
Please comment if there is anything else to modify or add.
The output of
thefuck --version
(something likeThe Fuck 3.1 using Python 3.5.0 and Bash 4.4.12(1)-release
):Your system (Debian 7, ArchLinux, Windows, etc.):
How to reproduce the bug:
The output of The Fuck with
THEFUCK_DEBUG=true
exported (typically executeexport THEFUCK_DEBUG=true
in your shell before The Fuck):If the bug only appears with a specific application, the output of that application and its version:
Anything else you think is relevant: