diff options
| author | bors <bors@rust-lang.org> | 2021-05-15 05:20:49 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2021-05-15 05:20:49 +0000 |
| commit | 428636f954204abb8a561a0bd08dc340fc0985c0 (patch) | |
| tree | d679746e5d66a484f90e9159f14b291fb17e5361 /compiler/rustc_codegen_llvm/src | |
| parent | 1025db84a68b948139b5adcd55da31bce32da8f3 (diff) | |
| parent | a8da3335e6e6f6d6ad8500205ded61a5351dc2b4 (diff) | |
| download | rust-428636f954204abb8a561a0bd08dc340fc0985c0.tar.gz rust-428636f954204abb8a561a0bd08dc340fc0985c0.zip | |
Auto merge of #84997 - pietroalbini:ci-verify-channel, r=Mark-Simulacrum
Error out if a PR is sent to the wrong channel It happened multiple times that a PR meant to go on beta ends up being opened (and occasionally merged) to master. This PR does two things: * Moves the definition of the channel in `src/ci/channel` so it's easier for tools to read it. I was not sure whether to move it to `src/channel` (like `src/version`): ended up with `src/ci` as it's currently only used for CI, but I'm open to moving it to `src`. We'll need to update the release process after this. * Adds a check on **non-bors** builds that errors out if the base branch is not the expected one for the currently defined channel. This will not cause problems for promotion PRs, as those PRs are meant to also update the channel name. r? `@Mark-Simulacrum`
Diffstat (limited to 'compiler/rustc_codegen_llvm/src')
0 files changed, 0 insertions, 0 deletions