@@ -9,7 +9,7 @@ team: the release team <https://www.rust-lang.org/governance/teams/operations#re
99If you've contributed to Rust before, you have likely used a command like this
1010to [ set labels] [ rustbot-labeling-docs ] :
1111
12- > @ ** rustbot** modify labels: A-typesystem C-enhancement
12+ > ** @ rustbot ** modify labels: A-typesystem C-enhancement
1313
1414Setting labels on issues and pull requests helps us keep track of and filter
1515issues. There are many kinds of labels you can set to mark an issue
@@ -30,7 +30,7 @@ So we have now [added the ability][regression-label-pr] for *anyone* to set
3030regression labels on issues! This is all you have to do to mark an issue as a
3131regression and it will automatically be prioritized:
3232
33- > @ ** rustbot** modify labels: regression-from-stable-to-{release-channel}
33+ > ** @ rustbot ** modify labels: regression-from-stable-to-{release-channel}
3434
3535Just replace ` {release-channel} ` with one of ` nightly ` , ` beta ` , or ` stable ` ,
3636depending on when the regression occurred, and you're good to go!
@@ -42,7 +42,7 @@ regression and providing information that will help us fix the issue.
4242Finally, if you have an issue that is * not* a regression, but is still something
4343that is important to be fixed, you can request prioritization with:
4444
45- > @ ** rustbot** prioritize
45+ > ** @ rustbot ** prioritize
4646
4747We really appreciate it if you mark all regressions with an appropriate label
4848so we can track them and fix them as soon as possible!
0 commit comments