Skip to content

Commit f9b2dea

Browse files
bors[bot]matklad
andauthored
Merge #6228
6228: Introduce S-actionable and S-unactionable labels r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
2 parents 3e450cf + 1900111 commit f9b2dea

File tree

1 file changed

+6
-1
lines changed

1 file changed

+6
-1
lines changed

docs/dev/README.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,12 @@ https://rust-lang.zulipchat.com/#narrow/stream/185405-t-compiler.2Fwg-rls-2.2E0
3535
* [E-easy](https://github.com/rust-analyzer/rust-analyzer/issues?q=is%3Aopen+is%3Aissue+label%3AE-easy),
3636
[E-medium](https://github.com/rust-analyzer/rust-analyzer/issues?q=is%3Aopen+is%3Aissue+label%3AE-medium),
3737
[E-hard](https://github.com/rust-analyzer/rust-analyzer/issues?q=is%3Aopen+is%3Aissue+label%3AE-hard),
38-
labels are *estimates* for how hard would be to write a fix.
38+
[E-unknown](https://github.com/rust-analyzer/rust-analyzer/issues?q=is%3Aopen+is%3Aissue+label%3AE-unknown),
39+
labels are *estimates* for how hard would be to write a fix. Each triaged issue should have one of these labels.
40+
* [S-actionable](https://github.com/rust-analyzer/rust-analyzer/issues?q=is%3Aopen+is%3Aissue+label%3AS-actionable) and
41+
[S-unactionable](https://github.com/rust-analyzer/rust-analyzer/issues?q=is%3Aopen+is%3Aissue+label%3AS-unactionable)
42+
specify if there are concrete steps to resolve or advance an issue. Roughly, actionable issues need only work to be fixed,
43+
while unactionable ones are effectively wont-fix. Each triaged issue should have one of these labels.
3944
* [fun](https://github.com/rust-analyzer/rust-analyzer/issues?q=is%3Aopen+is%3Aissue+label%3Afun)
4045
is for cool, but probably hard stuff.
4146

0 commit comments

Comments
 (0)