-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Call-for-testing without an RFC? #5222
Comments
cc @U007D |
Thanks, @Urgau. @Nadrieril, yes, I can add Meanwhile, I will remember to add this issue to CfT next week. |
Thanks! I added such a label: https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Acall-for-testing (I modeled it on the similar-feeling |
Little ping so this makes it into next week's TWiR |
Got this added this week in 5282. Thanks @Nadrieril and @U007D! |
Thank you! |
@U007D Following our previous conversation on Reddit, maybe you could add Rustup to the mix? I've made the first issue with the tag, maybe that'd be a good starting point: rust-lang/rustup#3806 |
Hi! I see the
call-for-testing
label can be applied on therust-lang/rfcs
repo to get mentioned in TWiR. I have a feature without an RFC here that I'd like to get tested. Would it be possible to have a similar label onrust-lang/rust
issues as well?The text was updated successfully, but these errors were encountered: