Skip to main content

This version of GitHub Enterprise Server was discontinued on 2024-09-25. 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 Server. For help with the upgrade, contact GitHub Enterprise support.

Managing workflow runs

You can manually interact with workflow runs to ensure they run effectively.

Manually running a workflow

When a workflow is configured to run on the workflow_dispatch event, you can run the workflow using the Actions tab on GitHub, GitHub CLI, or the REST API.

Re-running workflows and jobs

You can re-run a workflow run, all failed jobs in a workflow run, or specific jobs in a workflow run up to 30 days after its initial run.

Canceling a workflow

You can cancel a workflow run that is in progress. When you cancel a workflow run, GitHub cancels all jobs and steps that are a part of that workflow.

Disabling and enabling a workflow

You can disable and re-enable a workflow using the GitHub UI, the REST API, or GitHub CLI.

Skipping workflow runs

You can skip workflow runs triggered by the push and pull_request events by including a command in your commit message.

Deleting a workflow run

You can delete a workflow run that has been completed, or is more than two weeks old.

Downloading workflow artifacts

You can download archived artifacts before they automatically expire.

Removing workflow artifacts

You can reclaim used GitHub Actions storage by deleting artifacts before they expire on GitHub Enterprise Server.

Approving workflow runs from public forks

When an outside contributor submits a pull request to a public repository, a maintainer with write access may need to approve some workflow runs.

Approving workflow runs from private forks

When someone without write access submits a pull request to a private repository, a maintainer may need to approve any workflow runs.