-
Notifications
You must be signed in to change notification settings - Fork 710
Update PR and issue templates #8511
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
Comments
Actually, a reference to CONTRIBUTING.md is already made in the current PR template. |
I guess it's only to specific sections, but I agree this is enough. So only the issue templates remain to do. |
Do we (in general) want a “User questions” template? (edit: Ok, I am seeing what stack does and it correctly points first and foremost to Discourse). |
I'd say that's either Discourse or possibly the Discussions area. (Might be worth considering that it's very easy to switch something between Discussion and Issue on GH.) |
I don't have a strong feeling about questions. We don't receive many of those anyway. I just felt that it may seem more welcoming to have it. And I'd much rather answer Cabal questions here instead of anywhere else, but I realize that it may be undesirable for some reasons. |
I updated the description with a "simplified PR template". Please, share your thoughts! |
Where would I choose the simplified template? When I make a PR? Would it be default? |
@ffaf1 when you push the green button, just like with issues, no? I did double-check that GitHub allows several PR templates. |
Uh oh!
There was an error while loading. Please reload this page.
v2-
commands: they've been long the defaultOriginally posted by @Mikolaj in #6370 (comment)
Simplified PR template
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.
See also:
The text was updated successfully, but these errors were encountered: