diff options
| author | Yuki Okushi <huyuumi.dev@gmail.com> | 2021-03-03 16:27:42 +0900 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-03-03 16:27:42 +0900 |
| commit | 9b58b8b7f002c2ef8788f1bb85c53a33cb5cb690 (patch) | |
| tree | 360d28a1afdf9ffe95e2d62b3a94038965543e13 /compiler/rustc_mir/src/transform/coverage/debug.rs | |
| parent | b16b6820d3237d3deb7169c22c439a589d59bb70 (diff) | |
| parent | 59ee8725482b98efdef08c40185462e7fa148c4a (diff) | |
| download | rust-9b58b8b7f002c2ef8788f1bb85c53a33cb5cb690.tar.gz rust-9b58b8b7f002c2ef8788f1bb85c53a33cb5cb690.zip | |
Rollup merge of #82689 - camelid:rustdoc-nominated, r=Manishearth
meta: Notify Zulip for rustdoc nominated issues The rustdoc team does not currently use the `I-nominated` label, unlike the libs and compiler teams (and maybe others). One reason for this is that the other teams discuss their nominated issues in meetings, while rustdoc is an async-only team. However, it might be helpful to start using the `I-nominated` label for rustdoc. The team currently uses a `cc ``@rust-lang/rustdoc``` ping as the equivalent, but it's easier to track issues when they use `I-nominated`. Also we'd be more consistent with the other teams' procedures. Since rustdoc doesn't have meetings, I propose we instead use the triagebot notify Zulip functionality to create a topic in `#rustdoc` on Zulip and ping the team. So it would look a bit like the procedure for WG-prioritization when an issue acquires the `I-prioritize` label. cc ``@rust-lang/rustdoc`` for approval of the change r? ``@Mark-Simulacrum`` to make sure I configured triagebot correctly
Diffstat (limited to 'compiler/rustc_mir/src/transform/coverage/debug.rs')
0 files changed, 0 insertions, 0 deletions