diff options
| author | Matthias Krüger <476013+matthiaskrgr@users.noreply.github.com> | 2025-03-19 08:17:16 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-03-19 08:17:16 +0100 |
| commit | 09c28f8d3d8afd640fe2fe550dd57b8c07bd5f49 (patch) | |
| tree | 29c9cc4a4f8214d3a94520a60f3ca034e11de411 /compiler/rustc_codegen_llvm/src | |
| parent | 67d3e5e53fac8a2e923f0e938463482d47a63610 (diff) | |
| parent | 9dac4797beefe846fee0568bb6b1bd38a677425d (diff) | |
| download | rust-09c28f8d3d8afd640fe2fe550dd57b8c07bd5f49.tar.gz rust-09c28f8d3d8afd640fe2fe550dd57b8c07bd5f49.zip | |
Rollup merge of #138656 - Kobzol:post-merge-unnest, r=marcoieni
Remove double nesting in post-merge workflow
See [this](https://github.com/rust-lang/rust/pull/138630#issuecomment-2732224491) :)
Can be tested with:
```bash
#!/bin/bash
PARENT_COMMIT=493c38ba371929579fe136df26eccd9516347c7a
SHA=259fdb521200c9abba547302fc2c826479ef26b2
printf "<details>\n<summary>What is this?</summary>\n" >> output.log
printf "This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.\n" >> output.log
printf "</details>\n\n" >> output.log
cargo run --release post-merge-report ${PARENT_COMMIT} ${SHA} >> output.log
```
I think that it's better to leave the notice in CI, to avoid generating it in citool, which can also be executed locally.
r? `@marcoieni`
Diffstat (limited to 'compiler/rustc_codegen_llvm/src')
0 files changed, 0 insertions, 0 deletions