GitHub-Aktionen für ein Repository deaktivieren oder limitieren

Repository-Inhaber können GitHub Actions für ein bestimmtes Repository deaktivieren, aktivieren und limitieren.

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.

Über GitHub Actions-Berechtigungen für Dein Repository

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 zu GitHub Actions findest Du unter „Über GitHub Actions."

Du kannst GitHub Actions für Dein Repository aktivieren. Wenn Du GitHub Actions aktivierst, können Workflows Aktionen ausführen, die sich in Deinem Repository und jedem anderen öffentlichen Repository befinden. Du kannst GitHub Actions für Dein Repository komplett deaktivieren. Wenn Du GitHub Actions deaktivierst, werden keine Workflows in Deinem Repository ausgeführt.

Alternativ kannst Du GitHub Actions in Deinem Repository aktivieren, aber die Aktionen limitieren, die ein Workflow ausführen kann. When you enable local actions only, workflows can only run actions located in your repository, organization, or enterprise.

GitHub Actions-Berechtigungen für Dein Repository verwalten

You can disable all workflows for a repository or set a policy that configures which actions can be used in a repository.

If you choose Allow select actions, local actions are allowed, and there are additional options for allowing other specific actions. For more information, see "Allowing specific actions to run."

When you allow local actions only, the policy blocks all access to actions authored by GitHub. For example, the actions/checkout would not be accessible.

Note: You might not be able to manage these settings if your organization has an overriding policy or is managed by an enterprise account that has overriding policy. For more information, see "Disabling or limiting GitHub Actions for your organization" or "Enforcing GitHub Actions policies for your enterprise."

  1. Navigiere in GitHub Enterprise Server zur Hauptseite des Repository.
  2. Klicke unter Deinem Repository-Namen auf Settings (Einstellungen). Schaltfläche „Repository settings" (Repository-Einstellungen)
  3. Klicke in der linken Seitenleiste auf Actions (Aktionen).
  4. Under Actions permissions, select an option. Set actions policy for this organization
  5. Klicke auf Save (Speichern).

Allowing specific actions to run

When you choose Allow select actions, local actions are allowed, and there are additional options for allowing other specific actions:

  • Allow actions created by GitHub: You can allow all actions created by GitHub to be used by workflows. Actions created by GitHub are located in the actions and github organization. For more information, see the actions and github organizations.

  • Allow Marketplace actions by verified creators: You can allow all GitHub Marketplace actions created by verified creators to be used by workflows. When GitHub has verified the creator of the action as a partner organization, the badge is displayed next to the action in GitHub Marketplace.

  • Allow specified actions: You can restrict workflows to use actions in specific organizations and repositories.

    To restrict access to specific tags or commit SHAs of an action, use the same <OWNER>/<REPO>@<TAG OR SHA> syntax used in the workflow to select the action. For example, actions/javascript-action@v1.0.1 to select a tag or actions/javascript-action@172239021f7ba04fe7327647b213799853a9eb89 to select a SHA. For more information, see "Finding and customizing actions."

    You can use the * wildcard character to match patterns. For example, to allow all actions in organizations that start with space-org, you can specify space-org*/*. To add all actions in repositories that start with octocat, you can use */octocat*@*. For more information about using the * wildcard, see "Workflow syntax for GitHub Actions."

This procedure demonstrates how to add specific actions to the allow list.

  1. Navigiere in GitHub Enterprise Server zur Hauptseite des Repository.
  2. Klicke unter Deinem Repository-Namen auf Settings (Einstellungen). Schaltfläche „Repository settings" (Repository-Einstellungen)
  3. Klicke in der linken Seitenleiste auf Actions (Aktionen).
  4. Under Actions permissions, select Allow select actions and add your required actions to the list. Add actions to allow list
  5. Klicke auf Save (Speichern).

Enabling workflows for private repository forks

If you rely on using forks of your private repositories, you can configure policies that control how users can run workflows on pull_request events. Available to private repositories only, you can configure these policy settings for enterprise accounts, organizations, or repositories. For enterprise accounts, the policies are applied to all repositories in all organizations.

  • Run workflows from fork pull requests - Allows users to run workflows from fork pull requests, using a GITHUB_TOKEN with read-only permission, and with no access to secrets.
  • Send write tokens to workflows from pull requests - Allows pull requests from forks to use a GITHUB_TOKEN with write permission.
  • Send secrets to workflows from pull requests - Makes all secrets available to the pull request.

Configuring the private fork policy for a repository

  1. Navigiere in GitHub Enterprise Server zur Hauptseite des Repository.
  2. Klicke unter Deinem Repository-Namen auf Settings (Einstellungen). Schaltfläche „Repository settings" (Repository-Einstellungen)
  3. Klicke in der linken Seitenleiste auf Actions (Aktionen).
  4. Under Fork pull request workflows, select your options. Ein Beispiel: Aktiviere, deaktiviere oder limitiere die Aktionen für dieses Repository
  5. Click Save to apply the settings.

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.