Question

You are an enterprise owner for a GitHub Enterprise Cloud account. You created an enterprise-level security configuration that enables Dependabot alerts, secret scanning, and push protection, and you applied it to all organizations with the enforcement set so organizations cannot override it. One organization owner reports they need to disable push protection for a small set of legacy repositories that generate excessive false-positive blocks during migration. What is the correct way to accommodate this while keeping enterprise governance intact?

Accepted Answer

Because the enterprise configuration is enforced, the organization cannot override it; the enterprise owner must adjust enforcement or create/apply a different configuration for those repos

Answer

Instruct the organization owner to create an org-level security configuration that disables push protection and apply it to the legacy repos, which will automatically supersede the enterprise configuration

Answer

Tell the organization owner to delete the enterprise configuration from their organization so they can manage settings independently

Answer

Have individual repository admins toggle push protection off in each repository's Code security settings, since repo-level settings always win over enterprise settings