Org Secret Scanning Push Protection Bypass List
| action | Description | Sample | Rule |
|---|---|---|---|
| org_ | A role or team was added to the push protection bypass list at the organization level. | N | N |
| org_ | Push protection settings for "Users who can bypass push protection for secret scanning" changed from "Specific roles or teams" to "Anyone with write access" at the organization level. | N | N |
| org_ | Push protection settings for "Users who can bypass push protection for secret scanning" changed from "Anyone with write access" to "Specific roles or teams" at the organization level. | N | N |
| org_ | A role or team was removed from the push protection bypass list at the organization level. | N | N |
org_secret_scanning_push_protection_bypass_list.add
#Description
A role or team was added to the push protection bypass list at the organization level.
Documented on GitHub's enterprise audit log reference.
org_secret_scanning_push_protection_bypass_list.disable
#Description
Push protection settings for "Users who can bypass push protection for secret scanning" changed from "Specific roles or teams" to "Anyone with write access" at the organization level.
Documented on GitHub's enterprise audit log reference.
org_secret_scanning_push_protection_bypass_list.enable
#Description
Push protection settings for "Users who can bypass push protection for secret scanning" changed from "Anyone with write access" to "Specific roles or teams" at the organization level.
Documented on GitHub's enterprise audit log reference.
org_secret_scanning_push_protection_bypass_list.remove
#Description
A role or team was removed from the push protection bypass list at the organization level.
Documented on GitHub's enterprise audit log reference.