Why: governance.Engine.Authorize falls through to allowed when an org has no policies at all, so deny by default (#2078) is only as strong as the seeded policies. Deleting every policy, or an org that was never seeded, opens every authorized operation. Some delivery tests rely on the current behaviour.
Done when: an org with no applicable policy is refused for every authorized operation, the shipped policies grant what a fresh install needs, and the tests that leaned on the fall-through declare the policies they need.
**Why**: governance.Engine.Authorize falls through to allowed when an org has no policies at all, so deny by default (#2078) is only as strong as the seeded policies. Deleting every policy, or an org that was never seeded, opens every authorized operation. Some delivery tests rely on the current behaviour.
**Done when**: an org with no applicable policy is refused for every authorized operation, the shipped policies grant what a fresh install needs, and the tests that leaned on the fall-through declare the policies they need.
sam
added the highbug labels 2026-11-21 15:17:13 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Why: governance.Engine.Authorize falls through to allowed when an org has no policies at all, so deny by default (#2078) is only as strong as the seeded policies. Deleting every policy, or an org that was never seeded, opens every authorized operation. Some delivery tests rely on the current behaviour.
Done when: an org with no applicable policy is refused for every authorized operation, the shipped policies grant what a fresh install needs, and the tests that leaned on the fall-through declare the policies they need.