Docs: Clarify GitHub Actions re-run permissions for contributors#1842
Open
pranavchoudhary-tech wants to merge 3 commits into
Open
Docs: Clarify GitHub Actions re-run permissions for contributors#1842pranavchoudhary-tech wants to merge 3 commits into
pranavchoudhary-tech wants to merge 3 commits into
Conversation
Documentation build overview
|
hugovk
reviewed
Jun 19, 2026
Comment on lines
+704
to
+716
| 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. |
Member
There was a problem hiding this comment.
Suggested change
| 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. |
I think we can simplify this a little.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #1786.
The Developer Guide previously implied that any contributor could click the "Re-run jobs" button to retry a failing CI check. This updates the
pull-request-lifecycle.rstdocumentation to explicitly state that the button is only visible to core developers and triagers. It also provides alternative workarounds for regular contributors (e.g. asking a reviewer, pushing an empty commit, or closing/re-opening the PR).