@@ -9,7 +9,7 @@ team: the release team <https://www.rust-lang.org/governance/teams/operations#re
9
9
If you've contributed to Rust before, you have likely used a command like this
10
10
to [ set labels] [ rustbot-labeling-docs ] :
11
11
12
- > @ ** rustbot** modify labels: A-typesystem C-enhancement
12
+ > ** @ rustbot ** modify labels: A-typesystem C-enhancement
13
13
14
14
Setting labels on issues and pull requests helps us keep track of and filter
15
15
issues. 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
30
30
regression labels on issues! This is all you have to do to mark an issue as a
31
31
regression and it will automatically be prioritized:
32
32
33
- > @ ** rustbot** modify labels: regression-from-stable-to-{release-channel}
33
+ > ** @ rustbot ** modify labels: regression-from-stable-to-{release-channel}
34
34
35
35
Just replace ` {release-channel} ` with one of ` nightly ` , ` beta ` , or ` stable ` ,
36
36
depending 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.
42
42
Finally, if you have an issue that is * not* a regression, but is still something
43
43
that is important to be fixed, you can request prioritization with:
44
44
45
- > @ ** rustbot** prioritize
45
+ > ** @ rustbot ** prioritize
46
46
47
47
We really appreciate it if you mark all regressions with an appropriate label
48
48
so we can track them and fix them as soon as possible!
0 commit comments