Create issue templates #158
Conversation
beeankha
added
the
infrastructure
|
Do we also want templates for epics as well as documentation-related issues? Are there any other issue types that would be useful to add templates for? |
| title: '' | ||
| labels: enhancement, source::maintainer | ||
| assignees: '' | ||
|
|
There was a problem hiding this comment.
Is there a way we can restrict this option? Like can this only be shown for maintainers with some config flag?
There was a problem hiding this comment.
No, GH does offer the ability to restrict access to issue templates to select users
Right now I don't think we have "epics". Instead we have milestones that purely act as swim lanes to our Kanban board. I can't immediately think of any other template. I imagine most documentation, infrastructure, or testing requests will come from us (the maintainers). And from past experience, if a user wants to make a documentation change, it's easier to just put up a PR anyways. |
|
Any reason why we can't reuse the existing issue templates that we spend a lot of time on in the conda org? |
|
I expect that we will have different needs. Mostly because we started integrating with the GitHub project board and wanted to distinguish between maintainer issues and user issues. |
|
I think the biggest deal breaker right now is the lack of label customization. I would really like to auto-label issues as they come in to better organize the project board. It will make my life easier when I have to talk to our benefactors. |
Resolves #144