-
Notifications
You must be signed in to change notification settings - Fork 722
Revamp issue/PR templates #9100
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Terrific!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I feel like more could be said, but let's find out what as it gets used.
Some comments inline... We'd also need |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Otherwise looks okay.
Francesco, do you think you have energy to add |
I'm sorry, one more thing: can we also get `labels: ["attention: needs-review"] for the PR template? |
Are we sure we want to do that? What about drafts? |
Ok I have added two more templates and some user resources in #9102. |
I admit this is a bit bold but I think this is ultimately a good thing:
I went over a dozen PRs yesterday and noticed that those requiring our attention keep slipping through cracks. |
One more optional thing if you feel especially bold. People keep complaining about our PR template in that it has a long set of checkboxes that are not necessarily relevant for small contributions, and those are usually made by newcomers, so they get especially confused. Maybe, we need another template: something like "Documentation" or "User-invisible change" without any checkboxes. We also need a link to https://github.com/haskell/cabal/blob/master/CONTRIBUTING.md#github-pull-request-conventions in every PR template. |
I added For the simplified PR template I say: the idea is not bad let’s keep this in the scope of #8511 and discuss it in another issue! |
Gotcha, thanks so much!!! |
6b28b66
to
952b5fe
Compare
I split the template and added a link to Github PR conventions. That should be all for #8511. |
This looks paramount! Thank you! |
@mergify rebase |
* Add “Feature request” template * Integrate Artem’s review - `cabal` → Cabal - add “type: enhancement” label * Add “Documentation” issue template * Add labels to “Bug report” template. “type: bug” and ”needs-triage”. Suggested by Artem. * Add “Question” issue template * Fix typos Spotted by Brandon. * Fix English in “Question” template Fix by Brandon. Add “needs-review” to Pull Request template As suggested by Artem.
Split in full (PR modifies `cabal` behaviour) and simple (otherwise).
✅ Branch has been successfully rebased |
d83e14f
to
1a1a8c0
Compare
argh user question template is slightly off…
Il 12 luglio 2023 alle 08:53 mergify[bot] ha scritto:
… Merged #9100 into master.
--
Reply to this email directly or view it on GitHub:
#9100 (comment)
You are receiving this because you authored the thread.
Message ID: ***@***.***>
|
Closes #8511.
Adds “Feature Request”, “Documentation” and “Question” issue templates.
Splits PR template in two (simple and full one), adding PR Convetion link to both.
Please include the following checklist in your PR:
Any changes that could be relevant to users have been recorded in the changelog.N/AInclude manual QA notes if your PR relates to cabal-install.N/ABonus points for added automated tests!N/A