Fix formulations in label descriptions

This commit is contained in:
Philipp Krones 2021-01-15 11:30:58 +01:00 committed by GitHub
parent d72cb252f2
commit 8a77f63879
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -315,10 +315,10 @@ an ICE in a popular crate that many other crates depend on. We don't
want Clippy to crash on your code and we want it to be as reliable as the
suggestions from Rust compiler errors.
We have prioritization labels and sync-blocker label like below.
We have prioritization labels and a sync-blocker label, which are described below.
- [P-low][p-low]: Requires attention (fix/response/evaluation) by a team member but isn't urgent.
- [P-medium][p-medium]: Should be addressed by a team member until the next sync.
- [P-high][p-high]: Should be immediately addressed and will require a out-of-cycle sync or a backport.
- [P-high][p-high]: Should be immediately addressed and will require an out-of-cycle sync or a backport.
- [L-sync-blocker][l-sync-blocker]: An issue that "blocks" a sync.
Or rather: before the sync this should be addressed,
e.g. by removing a lint again, so it doesn't hit beta/stable.