From 4c05d7a6d432b6771df3048c24632844e1c3ee36 Mon Sep 17 00:00:00 2001 From: Dhruv Manilawala Date: Thu, 20 Jun 2024 23:19:43 +0530 Subject: [PATCH] Provide link on how to re-run all failed jobs (#11954) --- CONTRIBUTING.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 0e116b468d..d8aaac671c 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -351,7 +351,9 @@ even patch releases may contain [non-backwards-compatible changes](https://semve - The commit hash of the merged release pull request on `main` 1. The release workflow will do the following: 1. Build all the assets. If this fails (even though we tested in step 4), we haven't tagged or - uploaded anything, you can restart after pushing a fix. + uploaded anything, you can restart after pushing a fix. If you just need to rerun the build, + make sure you're [re-running all the failed + jobs](https://docs.github.com/en/actions/managing-workflow-runs/re-running-workflows-and-jobs#re-running-failed-jobs-in-a-workflow) and not just a single failed job. 1. Upload to PyPI. 1. Create and push the Git tag (as extracted from `pyproject.toml`). We create the Git tag only after building the wheels and uploading to PyPI, since we can't delete or modify the tag ([#4468](https://github.com/astral-sh/ruff/issues/4468)).