Restricting deploy keys in your organization

To protect your organization's data, you can configure permissions for creating deploy keys in your organization.

Wer kann dieses Feature verwenden?

Organization owners.

You can choose whether members can create deploy keys for repositories in your organization.

By default, new organizations are configured to disallow the creation of deploy keys in repositories.

Organization owners can restrict the creation of deploy keys to help prevent sensitive information from being exposed. For more information, see "Best Practices zum Verhindern von Datenlecks in deiner Organisation" and "Verwalten von Bereitstellungsschlüsseln." If you want more fine-grained control over permissions, consider using a GitHub App instead. See "GitHub-Apps – Übersicht."

If your organization is owned by an enterprise account, you may not be able to configure this setting for your organization, if an enterprise owner has set a policy at the enterprise level. For more information, see "Erzwingen von Repositoryverwaltungsrichtlinien in einem Unternehmen."

Warning

Changing this setting to disabled will result in existing deploy keys being disabled in all repositories in the organization. Scripts, apps, or workflows that create, use, or delete deploy keys will no longer work.

  1. Wählen Sie in der oberen rechten Ecke von GitHub Ihr Profilfoto aus, und klicken Sie dann auf Ihre Organisationen.
  2. Klicke neben der Organisation auf Einstellungen.
  3. Klicke im Abschnitt „Zugriff“ der Seitenleiste auf Mitgliederberechtigungen.
  4. Under "Deploy keys", review the information about changing the setting, click Enabled or Disabled.
  5. Click Save.