| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
(It's the first time I've tried setting up issue templates, so please review carefully.) |
Sorry, something went wrong.
There was a problem hiding this comment.
Looks good!
To compare with Mypy, will be something like: https://github.com/python/mypy/issues/new/choose
Sorry, something went wrong.
Co-authored-by: Hugo van Kemenade <hugovk@users.noreply.github.com>
There was a problem hiding this comment.
One last thing.
We can also skip "please" for brevity.
The Google style guide is pretty good, and says:
https://developers.google.com/style/tone?hl=en#politeness-and-use-of-please
Sorry, something went wrong.
Co-authored-by: Hugo van Kemenade <hugovk@users.noreply.github.com>
Co-authored-by: Hugo van Kemenade <hugovk@users.noreply.github.com>
Co-authored-by: Hugo van Kemenade <hugovk@users.noreply.github.com>
There was a problem hiding this comment.
Thank you!
Sorry, something went wrong.
There was a problem hiding this comment.
Looks mostly good to me, at least as a first iteration.
A few comments:
Sorry, something went wrong.
There was a problem hiding this comment.
Nice!
Sorry, something went wrong.
Co-authored-by: Ezio Melotti <ezio.melotti@gmail.com> Co-authored-by: Erlend Egeberg Aasland <erlend.aasland@innova.no>
Co-authored-by: Ezio Melotti <ezio.melotti@gmail.com>
Co-authored-by: Ezio Melotti <ezio.melotti@gmail.com>
|
It looks like there are 179 open issues that have the "build" label, but don't have any of "type-bug", "docs", "type-security" or "type-feature". I think I'd rather not create a build.md template, as I think if we have too many options it will just complicate things unnecessarily -- but I thought I'd mention it. |
Sorry, something went wrong.
Neither am I, tbh, but as you say -- they're not really for us; they're for people who are new to CPython :)
We could do that -- I've seen other projects do that. I don't think that's essential, though. CPython has a fairly active group of triagers and core devs who will generally be sifting through recently opened issues anyway. Most of the time, invalidly applied labels will be spotted fairly quickly; and if not, I don't think it's that big a deal anyway. |
Sorry, something went wrong.
There was a problem hiding this comment.
A couple more nits and then it's good to go:
Sorry, something went wrong.
Co-authored-by: Ezio Melotti <ezio.melotti@gmail.com>
|
Thanks everybody for the reviews! |
Sorry, something went wrong.
|
Thanks for the PR! It looks like we have 3 security-related entries now: https://github.com/python/cpython/issues/new/choose |
Sorry, something went wrong.
|
It might actually be better to remove the .github/ISSUE_TEMPLATE/security.md file too, and just leave the default security entry. What do you think? |
Sorry, something went wrong.
Yup, I think that's best! I had no idea having the .github/SECURITY.md would mean we'd have the duplicate entries. One is enough. |
Sorry, something went wrong.
|
Sorry, something went wrong.
This is because "build" used to be a type on bpo, and now it's a label on its own, since you can have both build-related features and bugs. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
A first step towards:
These are largely derived from the mypy issue templates, which I think are pretty effective (more effective than what CPython has currently, anyway 🙂)