Release Routing Policy Wheel
How to use: Spin to pick the routing treatment for the next release event.
All 4 routing options
Interrupt now for broken default-branch CISame-day alert for owner-blocking reviewDaily digest for issue state changesSuppress repeat success pings
About the Release Routing Policy Wheel
Use this wheel when a release team needs to choose how an event should be routed without turning every signal into an interruption. It helps distinguish critical breakages from owner-blocking handoffs, medium-signal updates, and low-value success churn. The options reflect a digest-first notification approach: interrupt only when action is urgent, alert same-day when a person is blocked, batch medium-signal issue movement, and suppress redundant success pings. This makes it easier to keep one clear operator lane instead of scattering updates across channels.