Note: GitHub Actions support on GitHub Enterprise Server 2.22 is a limited public beta. To review the external storage requirements and request access to the beta, see "Enabling GitHub Actions and configuring storage."
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.
Informationen zur Abrechnung für GitHub Actions
GitHub Actions usage is free for GitHub Enterprise Server that use self-hosted runners.
Nutzungseinschränkungen
Usage limits apply to self-hosted runners. Weitere Informationen findest Du unter „Informationen zu selbst-gehosteten Runnern“.
GitHub Actions für Dein Repository oder Deine Organisation deaktivieren oder beschränken
By default, after GitHub Actions is enabled on your GitHub Enterprise Server instance, it is enabled on all repositories and organizations. You can choose to disable GitHub Actions or limit them to private actions only, which means that people can only use actions that exist in your repository.
Weitere Informationen findest Du unter:
- "Disabling or limiting GitHub Actions for a repository"
- "Disabling or limiting GitHub Actions for your organization"
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."