Update issue templates #64983
Update issue templates #64983
Conversation
zimbatm
force-pushed
the
new-issue-template
branch
from
a50e6d3
to
fd15c25
Compare
ofborg
bot
added
6.topic: policy discussion
10.rebuild-darwin: 0
10.rebuild-linux: 0
labels
|
I like to have a couple templates. Important is, though, that there is a general one in case others don't apply, and that it is obvious which one that is and that it is OK to take that one when not sure. I think the general issue should be the default one. Suggested templates:
|
|
In that case I need to make some more tests. The UI only has 3 entries with pre-defined names: https://github.com/NixOS/nixpkgs/issues/templates/edit |
|
Note the motivation for these is because its not something ofborg can handle (unless we add some more advanced NLP to it). |
|
💥 this is a nice opportunity to add an attrset path selector to the issue template. This would allow ofborg to map an issue to a maintainer for us. |
|
After doing a bit of experimentation on my own repo, there is a limit of 3 templates available. + a generic one in small.
|
|
Cool! How about "regular" -> "miscellaneous" Also, upgrade requests seem to be reasonably common. Should they be a separate template, or go under "package requests"? |
|
We can only have 3 templates so we have to choose carefully. The "open a regular issue" text is not something we control. |
|
The "Open a regular issues." link uses the old |
|
I'm going to make another pass at the templates to add a front-matter for the structured data |
Create new categories for the issues: * Bug report * Packaging request * Security Add metadata information to the issues so that we may match issues to maintainers using a bot in the future. The old `.github/ISSUE_TEMPLATE.md` is being used by the "Open a regular issue." link.
zimbatm
force-pushed
the
new-issue-template
branch
from
fd15c25
to
51181f8
Compare
|
Okay this is ready for review. You can play with the new issue templates over here to see how it will look like: https://github.com/zimbatm/nixpkgs/issues/new/choose |
|
TODO from @ghuntley: add a untriaged label |
|
Not applicable for these files, but for the other .github/ ones it may be worth it to put them all in one repo: |
|
@ghuntley showed us a repo with more than 3 templates during the office hours. So maybe we can add many more. |
|
I would be interested in an issue template (and label) for grahamc/r13y.com#3 The idea being I could have a link to a search page, like "autogen-5.18.12. is unreproducible label:reproducibility" |
|
I'll merge this for now to expose the changes to a wider public so we can iterate on the templates. |
Use the new issue template format and add a "packaging request" template.
The best thing is that labels are pre-applied so they are then easily queryable.