Skip to content

Docs: Clarify GitHub Actions re-run permissions for contributors #1842

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
pranavchoudhary-tech wants to merge 3 commits into
base: main
Choose a base branch
from
+13 −4
Open

Docs: Clarify GitHub Actions re-run permissions for contributors #1842

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
d586671
Docs: Clarify GitHub Actions re-run permissions for contributors
pranavchoudhary-tech Jun 19, 2026
dd68c78
[pre-commit.ci] auto fixes from pre-commit.com hooks
pre-commit-ci[bot] Jun 19, 2026
f028dfb
Apply review suggestions
pranavchoudhary-tech Jun 19, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 13 additions & 4 deletions getting-started/pull-request-lifecycle.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

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.

Re-running failed jobs shouldn't be your first instinct but it is occasionally
helpful because distributed systems can have intermittent failures, and
Expand Down
Loading