-
-
Notifications
You must be signed in to change notification settings - Fork 32.1k
Improve the GitHub issue templates #107150
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
I see we get the full CPython test suite run on PRs that edit the GitHub issue templates 😆 |
Co-authored-by: Ezio Melotti <ezio.melotti@gmail.com>
…ood/cpython into improve-issue-templates
Ready to merge? |
I was giving it a few days to give anybody else who wanted to a chance to give feedback — but yes, I think we can merge now! |
Should we backport this to 3.12 and 3.11? It probably wouldn't do any harm, right? |
Thanks! They'll only have effect in the default branch, so don't need to be backported, but will do no harm :) |
Oh, of course, it's an issue template, not a PR template, and there's no way to make an issue "targeting a different branch" in the same way as a PR 🤦♂️ We can leave it, then, there's no point backporting! |
Thanks, both! |
bug.md
template shorterbug.md
template into a checklist, so that it's clear that these are steps we expect of issue reporters (not optional things-to-consider!)feature.md
template why we'd like people to post on discuss.python.org before opening a feature request on GitHub (and move the "please post on discuss.python.org" notice to the top of the form).