Is your feature request related to a use case or problem?
I feel like the use of GitHub YAML-based issue forms is a failure. On paper, it seems like a good idea, and the web interface is nice enough, but:
-
On the command-line, gh issue create does not handle them -- in fact, it doesn't even know they exist. Conversely, Markdown-based issue templates work fine, including when you open an external editor.
-
There was a hope that maybe GitHub would add proper support for YAML-based issue templates in gh eventually, but that still has not happened.
-
The YAML version of templates is harder and more error-prone to edit and maintain.
Mea culpa because the push for using the YAML templates in the first place was my idea, but this is not worth it. Let's go back to using Markdown templates.
What solution or approach do you envision?
We have a starting point in the (private) template directory in Quantumlib, so the switch will not take long.
How urgent is this for you?
None
Is your feature request related to a use case or problem?
I feel like the use of GitHub YAML-based issue forms is a failure. On paper, it seems like a good idea, and the web interface is nice enough, but:
On the command-line,
gh issue createdoes not handle them -- in fact, it doesn't even know they exist. Conversely, Markdown-based issue templates work fine, including when you open an external editor.There was a hope that maybe GitHub would add proper support for YAML-based issue templates in
gheventually, but that still has not happened.The YAML version of templates is harder and more error-prone to edit and maintain.
Mea culpa because the push for using the YAML templates in the first place was my idea, but this is not worth it. Let's go back to using Markdown templates.
What solution or approach do you envision?
We have a starting point in the (private) template directory in Quantumlib, so the switch will not take long.
How urgent is this for you?
None