-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Use new template forms for issue templates #8032
Conversation
r? @camsteffen (rust-highfive has picked a reviewer for you, use r? to override) |
Of course there is still the question if we want to do this. I'll bring it up in the meeting on Tuesday. |
Very fancy, I like this a lot! 👍 |
I'd like to see error output for false positive and lint name (optional) for new lint. But that's orthogonal to using the fancy new forms, so I think this is good! |
I modified the default value of the text area. I think adding an additional section for just an error output would be overkill. |
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.
r=me after squash. Thanks!
GitHub has a new way to define issue templates. This gives an even more consistent formatting of our issues.
1b14d2a
to
11002c7
Compare
Rebased+Squashed. Let's get this merged. @bors r=camsteffen |
📌 Commit 11002c7 has been approved by |
☀️ Test successful - checks-action_dev_test, checks-action_remark_test, checks-action_test |
GitHub has a new way to define issue templates. This gives an even more consistent formatting of our issues.
You can find (read-only) rendered versions here. If you want to try to fill out this kind of issue, you can do this in the
cargo
Repo.changelog: Better issue templates