Skip to main content
� 

� 

This version of GitHub Enterprise was discontinued on 2022-10-12. No patch releases will be made, even for critical security issues. For better performance, improved security, and new features, upgrade to the latest version of GitHub Enterprise. For help with the upgrade, contact GitHub Enterprise support.

Re-running workflows and jobs

In this article

You can re-run a workflow run up to 30 days after its initial run.

Who can use this feature

People with write permissions to a repository can re-run workflows in the repository.

Note: GitHub-hosted runners are not currently supported on GitHub Enterprise Server. You can see more information about planned future support on the GitHub public roadmap.

About re-running workflows and jobs

Re-running a workflow uses the same GITHUB_SHA (commit SHA) and GITHUB_REF (Git ref) of the original event that triggered the workflow run. You can re-run a workflow for up to 30 days after the initial run.

Re-running all the jobs in a workflow

  1. On your GitHub Enterprise Server instance, navigate to the main page of the repository.

  2. Under your repository name, click Actions. Actions tab in the main repository navigation

  3. In the left sidebar, click the workflow you want to see. Workflow list in left sidebar

  4. From the list of workflow runs, click the name of the run to see the workflow run summary.

    Name of workflow run

  5. In the upper-right corner of the workflow, use the Re-run jobs drop-down menu, and select Re-run all jobs.

    Re-run checks drop-down menu

To learn more about GitHub CLI, see "About GitHub CLI."

To re-run a failed workflow run, use the run rerun subcommand. Replace run-id with the ID of the failed run that you want to re-run. If you don't specify a run-id, GitHub CLI returns an interactive menu for you to choose a recent failed run.

gh run rerun RUN_ID

To view the progress of the workflow run, use the run watch subcommand and select the run from the interactive list.

gh run watch