aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorbors[bot] <26634292+bors[bot]@users.noreply.github.com>2021-02-01 14:46:56 +0000
committerGitHub <[email protected]>2021-02-01 14:46:56 +0000
commit2d9bb69990b866bad0b4300972f1706d38329ad3 (patch)
treece31f376ac2604b2fa476ae17fa70a7ad5be7928
parent746b89d1c383a30a7b2d5168724261dded613b93 (diff)
parent5e61d62fdcae88e528ff3dcfb97253eb9ea1d4b8 (diff)
Merge #7507
7507: Explain what to do if a release fails r=lnicola a=lnicola bors r+ Co-authored-by: LaurenČ›iu Nicola <[email protected]>
-rw-r--r--docs/dev/README.md4
1 files changed, 4 insertions, 0 deletions
diff --git a/docs/dev/README.md b/docs/dev/README.md
index 6bce38e56..4cc608b07 100644
--- a/docs/dev/README.md
+++ b/docs/dev/README.md
@@ -302,6 +302,10 @@ Release steps:
3025. Inside `rust-analyzer`, run `cargo xtask promote` -- this will create a PR to rust-lang/rust updating rust-analyzer's submodule. 3025. Inside `rust-analyzer`, run `cargo xtask promote` -- this will create a PR to rust-lang/rust updating rust-analyzer's submodule.
303 Self-approve the PR. 303 Self-approve the PR.
304 304
305If the GitHub Actions release fails because of a transient problem like a timeout, you can re-run the job from the Actions console.
306If it fails because of something that needs to be fixed, remove the release tag (if needed), fix the problem, then start over.
307Make sure to remove the new changelog post created when running `cargo xtask release` a second time.
308
305# Permissions 309# Permissions
306 310
307There are three sets of people with extra permissions: 311There are three sets of people with extra permissions: