[Proposal]: Use new GitHub's form schema for Issue forms #319
Labels
ENHANCEMENT ⚡
New Feature/Addition/Improvement
PROPOSAL 📩
A proposal/proposition
SOLVED 🏁
This issue/PR is resolved now. Goal Achieved!
Projects
Milestone
Brief Description
GitHub's form schema that uses YAML instead of markdown is currently in beta. These new YAML Issue GitHub's form schema have a lot of major benefits that this repository could benefit from:
Advantages over traditional Markdown Issue forms?
required: true
marked fields cannot be ignored and will make the user require to fill out the field, select an option or similar before they can submit an issue.For more information see: https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema
Context
GitHub's form schema for those who don't know are essentially enhanced Issue templates, allowing more freedom in designing issue templates. There is a page providing some info about the new GitHub's form schema issue forms: https://gh-community.github.io/issue-template-feedback/structured/
Any Other Important Information
Screenshot of new Bug Report form:
The text was updated successfully, but these errors were encountered: