Skip to main content
We publish frequent updates to our documentation, and translation of this page may still be in progress. For the most current information, please visit the English documentation.
All products
GitHub Actions

This version of GitHub Enterprise was discontinued on 2023-03-15. 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.

Removing workflow artifacts

In this article

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

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.

Deleting an artifact

Warning: Once you delete an artifact, it cannot be restored.

Write access to the repository is required to perform these steps.

By default, GitHub Enterprise Server stores build logs and artifacts for 90 days, and this retention period can be customized. For more information, see "Usage limits, billing, and administration."

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

  2. Under your repository name, click Actions.

    Screenshot of the tabs for the "github/docs" repository. The "Actions" tab is highlighted with an orange outline.

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

    Screenshot of the left sidebar of the "Actions" tab. A workflow, "CodeQL," is outlined in dark orange.

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

  5. Under Artifacts, click next to the artifact you want to remove.

    Screenshot showing artifacts created during a workflow run. A trash can icon, used to remove an artifact, is outlined in dark orange.

Setting the retention period for an artifact

Retention periods for artifacts and logs can be configured at the repository, organization, and enterprise level. For more information, see "Usage limits, billing, and administration."

You can also define a custom retention period for individual artifacts using the actions/upload-artifact action in a workflow. For more information, see "Storing workflow data as artifacts."

Finding the expiration date of an artifact

You can use the API to confirm the date that an artifact is scheduled to be deleted. For more information, see the expires_at value returned by "Actions."