Question

You are a repository administrator for a private repository in an organization that has a GitHub Advanced Security / Secret Protection license available but not yet enabled everywhere. Developers keep asking why they aren't getting warnings when they try to push AWS keys. You navigate to the repository's Settings > Advanced Security to turn on the protection. Which sequence correctly reflects the dependency you must satisfy before push protection can be enabled for this private repository?

Accepted Answer

Secret scanning must be enabled first; only then can push protection be turned on for the repository.

Answer

Push protection can be enabled independently and does not require secret scanning to be active.

Answer

Branch protection rules must be configured first, after which push protection becomes automatically active.

Answer

Dependency graph must be enabled first, since push protection relies on it to identify secret patterns.