@@ -18,9 +18,8 @@ We need to care for the Clippy project the same way that Clippy cares about our
18
18
code, and note that every single one of them needs maintaining and accounting
19
19
for current and future changes in the compiler as a whole.
20
20
21
- As a team we’ll focus on making contributing the best it can be, we’ll try to
22
- bisect all the issues possible and mark the issues that could be great as a
23
- starting point to get familiar with the project.
21
+ As a team we’ll focus on making contributing the best it can be, and mark the
22
+ issues that could be great as a starting point to get familiar with the project.
24
23
25
24
## What can I expect as a user?
26
25
@@ -41,7 +40,7 @@ be prioritized over bugfixes.
41
40
## Can I help?
42
41
43
42
As always, any help on the project is very appreciated. Apart from opening bug
44
- reports, you can follow our [ contributing guidelines] and check [ our suggested
43
+ reports, you can follow [ our contributing guidelines] and check [ our suggested
45
44
good first issues] for opening pull requests . Everything from fixing diagnostic
46
45
issues and improving documentation, to fixing application-wide crashes
47
46
really helps Clippy get into the excellent state that our users deserve.
@@ -56,7 +55,7 @@ Thanks a lot for all these years of supporting Clippy, we hope that via this
56
55
little feature hiatus we can achieve the excellence that the Rust user base
57
56
deserves (if that's even possible).
58
57
59
- [ contributing guidelines ] : https://github.com/rust-lang/rust-clippy/blob/master/CONTRIBUTING.md
58
+ [ our contributing guidelines] : https://github.com/rust-lang/rust-clippy/blob/master/CONTRIBUTING.md
60
59
[ our suggested good first issues ] : < !-- ADD HERE OUR TRACKING ISSUE -- >
61
60
62
61
0 commit comments