-
Notifications
You must be signed in to change notification settings - Fork 887
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Transition from .md to .yml for Issue Templates #4165
Comments
Venkatesh-Krishnan-R
added
the
spec:miscellaneous
For issues that don't match any other spec label
label
Jul 29, 2024
danielgblanco
added
triage:deciding:community-feedback
and removed
spec:miscellaneous
For issues that don't match any other spec label
labels
Jul 29, 2024
Hi there, I've removed the |
I'm glad to receive input from others on how we can streamline it :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What are you trying to achieve?
Transitioning our issue templates from Markdown (.md) files to YAML (.yml) files. This shift is intended to improve user interaction and streamline the issue-creation process. The aim is to provide a more intuitive and structured way for users to report bugs, request features, and provide feedback.
Advantages:
What did you expect to see?
Additional context.
Add any other context about the problem here. If you followed an existing documentation, please share the link to it.
I have attached a couple of screenshots showing how the structure looks and how the create issue page appears. I have currently only created it for one specification, and since it is working fine, I can proceed with creating it for the rest of the specifications.
Once it is reviewed, I can create a PR for the change
The text was updated successfully, but these errors were encountered: