Usage limits, billing, and administration

There are usage limits for GitHub Actions workflows. Usage charges apply to repositories that go beyond the amount of free minutes and storage for a repository.

Informationen zur Abrechnung für GitHub Actions

GitHub Actions usage is free for GitHub Enterprise Servers that use self-hosted runners.

Nutzungseinschränkungen

Usage limits apply to self-hosted runners. Weitere Informationen findest Du unter „Informationen zu selbst-gehosteten Runnern“.

Artifact and log retention policy

You can configure the artifact and log retention period for your repository, organization, or enterprise account.

By default, the artifacts and log files generated by workflows are retained for 90 days before they are automatically deleted. You can adjust the retention period, depending on the type of repository:

  • For public repositories: you can change this retention period to anywhere between 1 day or 90 days.
  • For private, internal, and GitHub Enterprise Server repositories: you can change this retention period to anywhere between 1 day or 400 days.

When you customize the retention period, it only applies to new artifacts and log files, and does not retroactively apply to existing objects. For managed repositories and organizations, the maximum retention period cannot exceed the limit set by the managing organization or enterprise.

Weitere Informationen findest Du unter:

GitHub Actions für Dein Repository oder Deine Organisation deaktivieren oder beschränken

By default, after GitHub Actions is enabled on your enterprise, it is enabled on all repositories and organizations. You can choose to disable GitHub Actions or limit them to local actions only, which means that people can only use actions that exist in your repository.

Weitere Informationen findest Du unter:

Disabling and enabling workflows

You can enable and disable individual workflows in your repository on GitHub.

To prevent unnecessary workflow runs, scheduled workflows may be disabled automatically. When a public repository is forked, scheduled workflows are disabled by default. In a public repository, scheduled workflows are automatically disabled when no repository activity has occurred in 60 days.

For more information, see "Disabling and enabling a workflow."

Did this doc help you?

Privacy policy

Help us make these docs great!

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

Oder, learn how to contribute.