
GitHub Repository Rulesets
GitHub changelog entry announcing two repository ruleset changes. Individual users can now be added as bypass actors on repository-level rulesets through the UI, REST API and GraphQL, so a dedicated team or role is no longer needed for a single person or service account. Repository admins can also rename a branch covered by an organization or enterprise ruleset, but only if the new name stays within the scope of every ruleset that applied to the old one. Otherwise the rename is blocked and an org or enterprise admin must do it, and org and enterprise admins can turn the capability off. This matters for branch-protection governance because bypass lists and rename rights affect who can circumvent required controls.
Technologies named here
Related in DevSecOps
JFrog: The Governance Gap Between Your Policy and Your Pipeline

Dev Machine Guard Now Supports Windows - StepSecurity

Socket: TanStack npm Packages Compromised
