From d586671bdc97447d72a76a3f92c89074d75eafac Mon Sep 17 00:00:00 2001 From: pranavchoudhary-tech Date: Fri, 19 Jun 2026 22:44:02 +0530 Subject: [PATCH 1/3] Docs: Clarify GitHub Actions re-run permissions for contributors --- getting-started/pull-request-lifecycle.rst | 17 +++++++++++++---- 1 file changed, 13 insertions(+), 4 deletions(-) diff --git a/getting-started/pull-request-lifecycle.rst b/getting-started/pull-request-lifecycle.rst index 78c8cfff0..c8dd304b0 100644 --- a/getting-started/pull-request-lifecycle.rst +++ b/getting-started/pull-request-lifecycle.rst @@ -701,10 +701,19 @@ list of executed checks. Clicking :guilabel:`Update branch` next to this message will merge in the latest changes from the base branch into the PR. If this still doesn't help with the failure on the PR, you can try -to re-run that particular failed check. Go to the red GitHub Action job, -click on the :guilabel:`Re-run jobs` button on the top right, and select -:guilabel:`Re-run failed jobs`. The button will only be present when all other -jobs finished running. +to re-run that particular failed check. + +Note that the :guilabel:`Re-run jobs` button on GitHub Actions is only visible +to Python core developers and triagers. If you have these permissions, go to +the red GitHub Action job, click on the :guilabel:`Re-run jobs` button on the +top right, and select :guilabel:`Re-run failed jobs`. The button will only be +present when all other jobs finished running. + +If you are a regular contributor and cannot see the button, you can ask a +reviewer to re-run the failed jobs for you in a PR comment. Alternatively, you +can re-trigger the CI by pushing an empty commit to your branch (e.g. +``git commit --allow-empty -m "Trigger CI"``), or by closing and re-opening +your pull request. Re-running failed jobs shouldn't be your first instinct but it is occasionally helpful because distributed systems can have intermittent failures, and From dd68c78f533812e95667672bd1b93c912f611baa Mon Sep 17 00:00:00 2001 From: "pre-commit-ci[bot]" <66853113+pre-commit-ci[bot]@users.noreply.github.com> Date: Fri, 19 Jun 2026 17:14:14 +0000 Subject: [PATCH 2/3] [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci --- getting-started/pull-request-lifecycle.rst | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/getting-started/pull-request-lifecycle.rst b/getting-started/pull-request-lifecycle.rst index c8dd304b0..2749bfa83 100644 --- a/getting-started/pull-request-lifecycle.rst +++ b/getting-started/pull-request-lifecycle.rst @@ -701,18 +701,18 @@ list of executed checks. Clicking :guilabel:`Update branch` next to this message will merge in the latest changes from the base branch into the PR. If this still doesn't help with the failure on the PR, you can try -to re-run that particular failed check. +to re-run that particular failed check. -Note that the :guilabel:`Re-run jobs` button on GitHub Actions is only visible -to Python core developers and triagers. If you have these permissions, go to -the red GitHub Action job, click on the :guilabel:`Re-run jobs` button on the -top right, and select :guilabel:`Re-run failed jobs`. The button will only be +Note that the :guilabel:`Re-run jobs` button on GitHub Actions is only visible +to Python core developers and triagers. If you have these permissions, go to +the red GitHub Action job, click on the :guilabel:`Re-run jobs` button on the +top right, and select :guilabel:`Re-run failed jobs`. The button will only be present when all other jobs finished running. -If you are a regular contributor and cannot see the button, you can ask a -reviewer to re-run the failed jobs for you in a PR comment. Alternatively, you -can re-trigger the CI by pushing an empty commit to your branch (e.g. -``git commit --allow-empty -m "Trigger CI"``), or by closing and re-opening +If you are a regular contributor and cannot see the button, you can ask a +reviewer to re-run the failed jobs for you in a PR comment. Alternatively, you +can re-trigger the CI by pushing an empty commit to your branch (e.g. +``git commit --allow-empty -m "Trigger CI"``), or by closing and re-opening your pull request. Re-running failed jobs shouldn't be your first instinct but it is occasionally From f028dfbbe8e38914c9fbd720ab5caca643b68645 Mon Sep 17 00:00:00 2001 From: pranavchoudhary-tech Date: Sat, 20 Jun 2026 00:22:13 +0530 Subject: [PATCH 3/3] Apply review suggestions --- getting-started/pull-request-lifecycle.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/getting-started/pull-request-lifecycle.rst b/getting-started/pull-request-lifecycle.rst index 2749bfa83..5dd56edb2 100644 --- a/getting-started/pull-request-lifecycle.rst +++ b/getting-started/pull-request-lifecycle.rst @@ -703,15 +703,15 @@ will merge in the latest changes from the base branch into the PR. If this still doesn't help with the failure on the PR, you can try to re-run that particular failed check. -Note that the :guilabel:`Re-run jobs` button on GitHub Actions is only visible -to Python core developers and triagers. If you have these permissions, go to +The :guilabel:`Re-run jobs` button on GitHub Actions is only visible +to Python core and triage teams. If you have these permissions, go to the red GitHub Action job, click on the :guilabel:`Re-run jobs` button on the top right, and select :guilabel:`Re-run failed jobs`. The button will only be present when all other jobs finished running. If you are a regular contributor and cannot see the button, you can ask a reviewer to re-run the failed jobs for you in a PR comment. Alternatively, you -can re-trigger the CI by pushing an empty commit to your branch (e.g. +can re-trigger the CI by pushing an empty commit to your branch (for example, ``git commit --allow-empty -m "Trigger CI"``), or by closing and re-opening your pull request.