-
-
Notifications
You must be signed in to change notification settings - Fork 14.2k
Add regression issue template #77725
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
Conversation
|
(rust_highfive has picked a reviewer for you, use r? to override) |
|
Squashed. Ready for review! |
d25e260 to
ccf6370
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
I'm worried that this template sort of intersects with both the Bug and ICE ones. How could we make it easier for a new bug reporter which template to use? |
|
#77769 landed |
Any ideas? :P |
|
Maybe change 'Bug' -> 'Existing Bug'? 'existing' is a little ambiguous if you don't know it's talking about releases, though ... |
|
Another issue is that people might not know what a "regression" is :/ |
I personally find it more confusing |
|
How about something like "Breakage on Stable Rust" |
If I'm not wrong a regression in this repository can be:
My suggestion "The issue breaks a previous Rust version"? edit: which is what LeSeulArtichaut wrote |
|
Please squash the commits; r=me after that. I imagine we'll want to iterate but seems good to get something merged in the meantime. |
bb0e53a to
91cc3d2
Compare
|
Squashed! |
|
@bors r+ rollup |
|
📌 Commit 91cc3d2 has been approved by |
Feel free to suggest improvements!