-
Notifications
You must be signed in to change notification settings - Fork 373
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add pull request template #487
Add pull request template #487
Conversation
Codecov Report
@@ Coverage Diff @@
## master #487 +/- ##
=======================================
Coverage 56.47% 56.47%
=======================================
Files 19 19
Lines 926 926
=======================================
Hits 523 523
Misses 350 350
Partials 53 53 Continue to review full report at Codecov.
|
I'm -1 b/c it's too long. I don't find the long PR/issue templates productive.
If all you're trying to address is these points, this will do:
|
We can definitely shorten more. Another goal is to remind submitters to add test. Sooo.. the checklist has become rather short and hard to ignore 😄 |
fbc45e9
to
052a108
Compare
Lets not do checklists if we can. Not everything warrants a test, and we can easily say please add tests. |
IMO lets not have any [ ] at all. I don’t want progress bars floating around for no good reason. Most people don’t even know GFM has that feature. If we can cap at 3 consecutive lines and no checkmarks I am happier. |
052a108
to
41dc8d3
Compare
Alright let's keep it minimal then. It's anyway just restating what is in our contributor guidelines. |
Do you mind removing empty lines. They aren’t required for newlines in PR descriptions. |
41dc8d3
to
b807c3a
Compare
Right, I should have known 🤣 |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ahmetb, corneliusweig The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
When small PRs are opened they often contain only very little description about the issue. In particular, they
This template should help out to improve this. Also, it explicitly mentions tests, so we hopefully see more of those :)