-
Notifications
You must be signed in to change notification settings - Fork 31
Yaml issue form #162
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
Yaml issue form #162
Conversation
| - type: input | ||
| id: radar | ||
| attributes: | ||
| label: "Radar URL" |
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.
a lot of people won't know what this is and I wonder if we should include it at all. If there is a bugzilla bug already, there will likely be a radar linked from it.... maybe we should drop this?
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.
It hasn't been an issue with the current template I think and it's kinda useful to have it. I suggest we keep it for now.
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.
imo, I think it's not a bad thing to discuss (again), but I don't think we should block changing the format of the form on this; it's really a totally difference change
marcoscaceres
left a comment
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.
Just a comment about the radar field... it's totally fine if it stays, but maybe worth considering dropping it.
|
FYI, the README.md (i.e., the second paragraph of https://github.com/WebKit/standards-positions) has a "file an issue" link that links directly to |
This is my attempt at converting the new issue template to use GitHub issue forms, as @gsnedders suggested. You can see how it renders here: https://github.com/hober/standards-positions/issues/new?assignees=&labels=&template=request-for-position.yml