diff options
| author | Stuart Cook <Zalathar@users.noreply.github.com> | 2025-10-03 09:16:28 +1000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-10-03 09:16:28 +1000 |
| commit | 179d182c83dbd70111595904383f13431b50a8ac (patch) | |
| tree | 984a8b79feec070c7a93e1899c9e2dec44fdfb7b /x.ps1 | |
| parent | 7a011558aa2be8b5049660727c8a0b661d21d0da (diff) | |
| parent | 16cfde9703f74cfc96c0c0bd51958a2627dfb5ea (diff) | |
| download | rust-179d182c83dbd70111595904383f13431b50a8ac.tar.gz rust-179d182c83dbd70111595904383f13431b50a8ac.zip | |
Rollup merge of #147263 - jieyouxu:disable-auto-backport-nominations, r=apiraino,Urgau
Disable triagebot auto stable-regression compiler backport nominations pending redesign Current auto compiler stable-regression backport nominations seem to be too aggressive, and seems to unfortunately lower signal-to-noise ratio of the compiler backport channel. So this PR disables the triagebot compiler auto stable-regression backport nominations pending a redesign. Beta-regression auto backport nominations are not modified, we might want to gather some more experience with it. No prejudice against re-enabling them if the nominations include a bit more context on _why_ it's automatically nominated and _which_ regression(s) are being addressed. Or as proposed, it could also simply become a reminder-to-nominate _comment_. cf. [#t-compiler/backports > #146919: stable-nominated @ 💬](https://rust-lang.zulipchat.com/#narrow/channel/474880-t-compiler.2Fbackports/topic/.23146919.3A.20stable-nominated/near/540979327) > I like the idea of rustbot just posting a message that suggests adding the label. That seems like a good compromise between avoiding forgotten nominations and avoiding spurious nominations. In any case, this was very much worth experimenting! r? `@apiraino` (or triagebot)
Diffstat (limited to 'x.ps1')
0 files changed, 0 insertions, 0 deletions