-
Notifications
You must be signed in to change notification settings - Fork 104
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
Issue template v2 #290
Issue template v2 #290
Conversation
Issue template using the GitHub Forms syntax.
Fix the `render` attribute in the `input` fields
Can one of the admins verify this patch? |
12 similar comments
Can one of the admins verify this patch? |
Can one of the admins verify this patch? |
Can one of the admins verify this patch? |
Can one of the admins verify this patch? |
Can one of the admins verify this patch? |
Can one of the admins verify this patch? |
Can one of the admins verify this patch? |
Can one of the admins verify this patch? |
Can one of the admins verify this patch? |
Can one of the admins verify this patch? |
Can one of the admins verify this patch? |
Can one of the admins verify this patch? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice, thank you!
@swift-server-bot test this please |
Change the current Issue form with a new one based on GitHub Forms 😎
Motivation:
The GitHub Forms syntax provide a way to design better issue forms defining sections with the most relevant information needed to understand and fix issues.
Another cool thing is that allow mark some fields as required
Extra ball: The issue report can be pre-filled with assign to and labels
Modifications:
Deleted the current issue template markdown file and added a new one in the
.github/ISSUE-TEMPLATE
folderThe repository must allow the new issue option at Settings
Result:
The issue form will look like this