Skip to content

Commit d44e35d

Browse files
Docs: Use spaces in good first issue label (#14844)
This unifies the Clippy repo with the rest of the rust org repos. changelog: none
2 parents 375c650 + 7123f2a commit d44e35d

File tree

3 files changed

+5
-5
lines changed

3 files changed

+5
-5
lines changed

CONTRIBUTING.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,7 @@ Clippy team directly by mentioning them in the issue or over on [Zulip]. All
5151
currently active team members can be found
5252
[here](https://github.com/rust-lang/rust-clippy/blob/master/triagebot.toml#L18)
5353

54-
Some issues are easier than others. The [`good-first-issue`] label can be used to find the easy
54+
Some issues are easier than others. The [`good first issue`] label can be used to find the easy
5555
issues. You can use `@rustbot claim` to assign the issue to yourself.
5656

5757
There are also some abandoned PRs, marked with [`S-inactive-closed`].
@@ -70,7 +70,7 @@ To figure out how this syntax structure is encoded in the AST, it is recommended
7070
Usually the lint will end up to be a nested series of matches and ifs, [like so][deep-nesting].
7171
But we can make it nest-less by using [let chains], [like this][nest-less].
7272

73-
[`E-medium`] issues are generally pretty easy too, though it's recommended you work on an [`good-first-issue`]
73+
[`E-medium`] issues are generally pretty easy too, though it's recommended you work on an [`good first issue`]
7474
first. Sometimes they are only somewhat involved code wise, but not difficult per-se.
7575
Note that [`E-medium`] issues may require some knowledge of Clippy internals or some
7676
debugging to find the actual problem behind the issue.
@@ -79,7 +79,7 @@ debugging to find the actual problem behind the issue.
7979
lot of methods that are useful, though one of the most useful would be `expr_ty` (gives the type of
8080
an AST expression).
8181

82-
[`good-first-issue`]: https://github.com/rust-lang/rust-clippy/labels/good-first-issue
82+
[`good first issue`]: https://github.com/rust-lang/rust-clippy/labels/good%20first%20issue
8383
[`S-inactive-closed`]: https://github.com/rust-lang/rust-clippy/pulls?q=is%3Aclosed+label%3AS-inactive-closed
8484
[`T-AST`]: https://github.com/rust-lang/rust-clippy/labels/T-AST
8585
[`T-middle`]: https://github.com/rust-lang/rust-clippy/labels/T-middle

book/src/development/the_team.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ this group to help with triaging, which can include:
3333

3434
1. **Labeling issues**
3535

36-
For the `good-first-issue` label, it can still be good to use `@rustbot` to
36+
For the `good first issue` label, it can still be good to use `@rustbot` to
3737
subscribe to the issue and help interested parties, if they post questions
3838
in the comments.
3939

triagebot.toml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
[relabel]
22
allow-unauthenticated = [
33
"A-*", "C-*", "E-*", "I-*", "L-*", "P-*", "S-*", "T-*",
4-
"good-first-issue", "beta-nominated"
4+
"good first issue", "beta-nominated"
55
]
66

77
# Allows shortcuts like `@rustbot ready`

0 commit comments

Comments
 (0)