From 5e61d62fdcae88e528ff3dcfb97253eb9ea1d4b8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lauren=C8=9Biu=20Nicola?= Date: Mon, 1 Feb 2021 16:43:18 +0200 Subject: Explain what to do if a release fails --- docs/dev/README.md | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'docs/dev/README.md') 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: 5. Inside `rust-analyzer`, run `cargo xtask promote` -- this will create a PR to rust-lang/rust updating rust-analyzer's submodule. Self-approve the PR. +If the GitHub Actions release fails because of a transient problem like a timeout, you can re-run the job from the Actions console. +If it fails because of something that needs to be fixed, remove the release tag (if needed), fix the problem, then start over. +Make sure to remove the new changelog post created when running `cargo xtask release` a second time. + # Permissions There are three sets of people with extra permissions: -- cgit v1.2.3