Why: #2078 reported that deleting the shipped org-workload policy has it seeded again on the next start, so revoking it means editing its text to a forbid. Since policies are now edited from the dashboard, the behaviour has to be deliberate and visible: an operator who deletes a shipped policy should know whether it comes back.
Done when: the behaviour for every shipped policy is decided and implemented one way (deletion sticks, or shipped policies can't be deleted and only edited), and the Policies page reflects it.
**Why**: #2078 reported that deleting the shipped org-workload policy has it seeded again on the next start, so revoking it means editing its text to a forbid. Since policies are now edited from the dashboard, the behaviour has to be deliberate and visible: an operator who deletes a shipped policy should know whether it comes back.
**Done when**: the behaviour for every shipped policy is decided and implemented one way (deletion sticks, or shipped policies can't be deleted and only edited), and the Policies page reflects it.
sam
added the mediumtask labels 2026-11-21 15:44:04 +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: #2078 reported that deleting the shipped org-workload policy has it seeded again on the next start, so revoking it means editing its text to a forbid. Since policies are now edited from the dashboard, the behaviour has to be deliberate and visible: an operator who deletes a shipped policy should know whether it comes back.
Done when: the behaviour for every shipped policy is decided and implemented one way (deletion sticks, or shipped policies can't be deleted and only edited), and the Policies page reflects it.