From c184f37034c3520a61b8dabd61159e6166336c8c Mon Sep 17 00:00:00 2001 From: pranavchoudhary-tech Date: Fri, 19 Jun 2026 22:44:02 +0530 Subject: [PATCH 1/4] 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 47f1100c2..ecd55ce54 100644 --- a/getting-started/pull-request-lifecycle.rst +++ b/getting-started/pull-request-lifecycle.rst @@ -667,10 +667,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 355e38bdebfee8687909d8d1c2aa522e0b767938 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/4] [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 ecd55ce54..4a6732bbb 100644 --- a/getting-started/pull-request-lifecycle.rst +++ b/getting-started/pull-request-lifecycle.rst @@ -667,18 +667,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 31729ed042081f1f284c99e861745b73e2b7b413 Mon Sep 17 00:00:00 2001 From: pranavchoudhary-tech Date: Sat, 20 Jun 2026 00:22:13 +0530 Subject: [PATCH 3/4] 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 4a6732bbb..48d7a9310 100644 --- a/getting-started/pull-request-lifecycle.rst +++ b/getting-started/pull-request-lifecycle.rst @@ -669,15 +669,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. From 5595a64daace50c31267095554e0f3f3a1595255 Mon Sep 17 00:00:00 2001 From: pranavchoudhary-tech Date: Sat, 4 Jul 2026 02:05:25 +0530 Subject: [PATCH 4/4] Apply review suggestions --- getting-started/pull-request-lifecycle.rst | 23 ++++++++++------------ 1 file changed, 10 insertions(+), 13 deletions(-) diff --git a/getting-started/pull-request-lifecycle.rst b/getting-started/pull-request-lifecycle.rst index 48d7a9310..351a99dbe 100644 --- a/getting-started/pull-request-lifecycle.rst +++ b/getting-started/pull-request-lifecycle.rst @@ -667,19 +667,16 @@ 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. - -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 (for example, -``git commit --allow-empty -m "Trigger CI"``), or by closing and re-opening -your pull request. +to re-run that particular failed check. Note that the :guilabel:`Re-run jobs` +button is only visible to members of the core and triage team. If you have those +permissions, go to the failed GitHub Action job, click :guilabel:`Re-run jobs` on +the top right, and select :guilabel:`Re-run failed jobs`. The button is only +present once all other jobs have finished. + +If don't have access to the button, ask a member of the teams to +re-run the jobs for you. Alternatively, you can re-trigger CI yourself by +pushing an empty commit, or by updating your branch with the +:guilabel:`Update branch` button. Re-running failed jobs shouldn't be your first instinct but it is occasionally helpful because distributed systems can have intermittent failures, and