Closed radumg closed 1 year ago
Totally agree, I've started using multiple issue templates on my repos, too. Just takes a couple of minutes to set it up.
Love it. Let me get some of the thoughts from the team and get this going. cc: @Racel @mjkkirschner @jnealb
Noticed some traction on this with this PR, DynamoDS/Dynamo#9150 . 😎 Figured I would add this here for tracking.
FYI, PR DynamoDS/Dynamo#9150 was replaced by DynamoDS/Dynamo#9393 which is now merged - not sure if adding these now would break that behaviour, needs to be tested.
The repo current has only 1, static issue template. Whilst very useful, there's a few limitations : (non-scientific evidence below...)
users only see the template text after clicking the new issue button -> things that shouldn't be an issue (
How do I...?
) will likely creep in as users won't abandon the issue form and press the bright & tempting greenSubmit new issue
button.several options are presented to the user in the text, but at that point, it's too late to choose and the links aren't clickable as they're in the input field
the text is populated in the issue form, so users have to manually delete irrelevant bits.
feature requests might want to ask different questions of the user vs bugs. currently not differentiated, requiring additional later work by maintainers.
Good news is these could be addressed with GitHub's multiple issue templates UI, see a great example here : https://github.com/symfony/symfony/issues/new/choose
This is just a suggestion, thought it might be timely since a little winter-cleaning is happening on the issues front 👏 🤓
For reference, current issue template text :