diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2024-04-17 18:01:37 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-04-17 18:01:37 +0200 |
| commit | d7d10707e015706e8817a92302ce3863617be2b4 (patch) | |
| tree | bc2f97a65e18e5d7dea34fc00c175eb8206777e4 /tests/rustdoc-js-std/parser-errors.js | |
| parent | 6c6b3027ef62e911142cfc55589baef4e9f38ec8 (diff) | |
| parent | 8f3d7fe0388c433008a91da14ef92de9a338b237 (diff) | |
| download | rust-d7d10707e015706e8817a92302ce3863617be2b4.tar.gz rust-d7d10707e015706e8817a92302ce3863617be2b4.zip | |
Rollup merge of #116957 - fmease:meta-notify-rustdoc-zulip-on-backport-nominations, r=GuillaumeGomez
meta: notify #t-rustdoc Zulip stream on backport nominations
In July '23, it was decided to handle rustdoc-specific backport nominations in t-rustdoc meetings going forward ([Zulip announcement](https://rust-lang.zulipchat.com/#narrow/stream/266220-t-rustdoc/topic/T-rustdoc.20backports/near/374828518)). However, t-rustdoc meetings are far too infrequent for them to address nominations on time (contrary to the weekly t-compiler meetings).
Hence GuillaumeGomez and I came to the conclusion that {beta,stable}-nominated rustdoc PRs should be dealt with on a case by case basis, e.g. on Zulip.
This PR attempts to partially automate this process. ~~Sadly, `triagebot` is not quite as flexible has I've hoped. Blocked on `triagebot` improvements (see the `FIXME`s in this PR).~~ (Fixed in rust-lang/triagebot#1791).
r? GuillaumeGomez
Diffstat (limited to 'tests/rustdoc-js-std/parser-errors.js')
0 files changed, 0 insertions, 0 deletions