-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Don't label tracking issues with needs-triage
#113515
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
Don't label tracking issues with needs-triage
#113515
Conversation
(rustbot has picked a reviewer for you, use r? to override) |
This comment has been minimized.
This comment has been minimized.
cc #113492 (comment). apparently this is non-deterministic too, ugh. cc @oli-obk @rust-lang/clippy, something in the switch to ui_test is breaking clippy tests. (more details in the linked comment) |
needs-triage
to tracking issuesneeds-triage
386f231
to
7d7f6c5
Compare
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.
we should probably triage tracking issues more, but triaging new ones really doesn't make sense
I believe I know what it is. I'll create a fix |
@bors r+ rollup |
r? Nilstrieb |
Rollup of 1 pull requests Successful merges: - rust-lang#113515 (Don't label tracking issues with `needs-triage`) r? `@ghost` `@rustbot` modify labels: rollup
Addresses #113261 (comment).
CC @Nilstrieb