@ops was in the registry but route.sh never routed to it. Adds ops to the routing loop + TOKEN_OPS case in route.sh/publish.sh and passes TOKEN_OPS in the workflow env. Required to trigger @ops at all.
@ops was in the registry but route.sh never routed to it. Adds ops to the routing loop + TOKEN_OPS case in route.sh/publish.sh and passes TOKEN_OPS in the workflow env. Required to trigger @ops at all.
PR #55 added @ops to the registry but route.sh only looped pm/junior/senior/lead/qa, so @ops could
never be triggered, and there was no token case for it. Add 'ops' to the routing loop and the
TOKEN_OPS case in route.sh + publish.sh, and pass TOKEN_OPS in the workflow env next to TOKEN_QA
(route/publish/rescue steps) so route.sh (set -u) doesn't error on an @ops run.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
@ops was in the registry but route.sh never routed to it. Adds ops to the routing loop + TOKEN_OPS case in route.sh/publish.sh and passes TOKEN_OPS in the workflow env. Required to trigger @ops at all.