GitHub Advanced Security customers can view an event in their organization or enterprise audit log when an admin enables or disables push protection for a custom pattern at the repository, organization, or enterprise level.
Today, we are announcing public beta of required workflows in GitHub Actions
Required workflows allow DevOps teams to define and enforce standard CI/CD practices across many source code repositories within an organization without needing to configure each repository individually. Organization admins can configure required workflows to run on all or selected repositories within the organization.
Required workflows will be triggered as required status checks for all the pull requests opened on the default branch, which blocks the ability to merge the pull request until the required workflow succeeds.
Individual development teams at the repository level will be able to see what required workflows have been applied to their repository.
In addition to reducing duplication of CI/CD configuration code, required workflows can also help companies with the following use cases:
- Security: Invoke external vulnerability scoring or dynamic analysis tools.
- Compliance: Ensure that all code meets an enterprise’s quality standards.
- Deployment: Ensure that code is continuously deployed in a standard way.