Skip to content
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

unauthenticated @rustbot label T-* #3494

Merged
merged 1 commit into from
Sep 20, 2023
Merged

unauthenticated @rustbot label T-* #3494

merged 1 commit into from
Sep 20, 2023

Conversation

eopb
Copy link
Contributor

@eopb eopb commented Sep 20, 2023

This is allowed in rust-lang/rust.

Others have also expected it to work in this repo:

@rustbot label not-rfc

@rustbot rustbot added the not-rfc For PRs that fix things like spelling mistakes, wrong file names, etc. label Sep 20, 2023
Copy link
Contributor

@ehuss ehuss left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems reasonable to me, thanks! The team assigned to an RFC is an important property, but I don't think this is likely going to be abused, and it is easy to repair if a mistake is made, and this can always be reverted if it is a problem.

@ehuss ehuss merged commit 3aef19f into rust-lang:master Sep 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
not-rfc For PRs that fix things like spelling mistakes, wrong file names, etc.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants