diff --git a/getting-started/pull-request-lifecycle.rst b/getting-started/pull-request-lifecycle.rst
index 78c8cfff0..5dd56edb2 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.
+
+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