Skip to content

Commit

Permalink
Bold '@' in @-mentions
Browse files Browse the repository at this point in the history
Thanks @LeSeulArtichaut! :)
  • Loading branch information
camelid committed Oct 13, 2020
1 parent 67d237a commit 3f4f1d5
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions posts/inside-rust/2020-10-08-regression-labels.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ team: the release team <https://www.rust-lang.org/governance/teams/operations#re
If you've contributed to Rust before, you have likely used a command like this
to [set labels][rustbot-labeling-docs]:

> @**rustbot** modify labels: A-typesystem C-enhancement
> **@rustbot** modify labels: A-typesystem C-enhancement
Setting labels on issues and pull requests helps us keep track of and filter
issues. There are many kinds of labels you can set to mark an issue
Expand All @@ -30,7 +30,7 @@ So we have now [added the ability][regression-label-pr] for *anyone* to set
regression labels on issues! This is all you have to do to mark an issue as a
regression and it will automatically be prioritized:

> @**rustbot** modify labels: regression-from-stable-to-{release-channel}
> **@rustbot** modify labels: regression-from-stable-to-{release-channel}
Just replace `{release-channel}` with one of `nightly`, `beta`, or `stable`,
depending on when the regression occurred, and you're good to go!
Expand All @@ -42,7 +42,7 @@ regression and providing information that will help us fix the issue.
Finally, if you have an issue that is *not* a regression, but is still something
that is important to be fixed, you can request prioritization with:

> @**rustbot** prioritize
> **@rustbot** prioritize
We really appreciate it if you mark all regressions with an appropriate label
so we can track them and fix them as soon as possible!
Expand Down

0 comments on commit 3f4f1d5

Please sign in to comment.