Repository navigation
ci(canary-rollout): list all registry agents in the dispatch input (#1045 part a) - #1047
Conversation
…1045 part a) The agent workflow_dispatch choice was hardcoded to [dev-lead], so manual evaluate/promote/rollback couldn't target the 6 #482 reusables now in the registry. List all 7 so they can be evaluated + promoted. (The gated SCHEDULED auto-promote — #1045 part b, decision A — remains for dev-lead.) Refs #1045, #1044.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe workflow_dispatch input ChangesCanary Rollout Agent Options
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related issues
Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
@donpetry-bot please review — trivial CI-config (agent input list), unblocks running the workflow. #1045 part a. |
Dev-Lead — waiting on PR blockers (intent: review-changes)PR: #1047 |
|
Note @don-petry I reviewed this PR and no code changes were needed, but it still has blocking checks or reviews (failing or cancelled checks, or changes-requested reviews), so I cannot mark it done yet. I'll re-check automatically. |
|
|
@don-petry I'm on it — starting a fresh review now. Results will appear in a few minutes. |
There was a problem hiding this comment.
Pull request overview
This PR updates the Canary Rollout workflow’s manual dispatch UI to allow selecting any agent registered for canary rollout, rather than being limited to dev-lead. This aligns the workflow_dispatch inputs with the expanded standards/canary-rings.json registry so operators can manually evaluate/promote/rollback the additional reusables introduced in the rollout plan.
Changes:
- Expanded
.github/workflows/canary-rollout.ymlworkflow_dispatch.inputs.agentchoice options from[dev-lead]to the full set of 7 registry agents.
…1045 part a) (#1047) The agent workflow_dispatch choice was hardcoded to [dev-lead], so manual evaluate/promote/rollback couldn't target the 6 #482 reusables now in the registry. List all 7 so they can be evaluated + promoted. (The gated SCHEDULED auto-promote — #1045 part b, decision A — remains for dev-lead.) Refs #1045, #1044. Co-authored-by: Claude Code Bot <bot@petry-projects>
…1045 part a) (#1047) The agent workflow_dispatch choice was hardcoded to [dev-lead], so manual evaluate/promote/rollback couldn't target the 6 #482 reusables now in the registry. List all 7 so they can be evaluated + promoted. (The gated SCHEDULED auto-promote — #1045 part b, decision A — remains for dev-lead.) Refs #1045, #1044. Co-authored-by: Claude Code Bot <bot@petry-projects>
…1045 part a) (#1047) The agent workflow_dispatch choice was hardcoded to [dev-lead], so manual evaluate/promote/rollback couldn't target the 6 #482 reusables now in the registry. List all 7 so they can be evaluated + promoted. (The gated SCHEDULED auto-promote — #1045 part b, decision A — remains for dev-lead.) Refs #1045, #1044. Co-authored-by: Claude Code Bot <bot@petry-projects>
…1045 part a) (#1047) The agent workflow_dispatch choice was hardcoded to [dev-lead], so manual evaluate/promote/rollback couldn't target the 6 #482 reusables now in the registry. List all 7 so they can be evaluated + promoted. (The gated SCHEDULED auto-promote — #1045 part b, decision A — remains for dev-lead.) Refs #1045, #1044. Co-authored-by: Claude Code Bot <bot@petry-projects>
…1045 part a) (#1047) The agent workflow_dispatch choice was hardcoded to [dev-lead], so manual evaluate/promote/rollback couldn't target the 6 #482 reusables now in the registry. List all 7 so they can be evaluated + promoted. (The gated SCHEDULED auto-promote — #1045 part b, decision A — remains for dev-lead.) Refs #1045, #1044. Co-authored-by: Claude Code Bot <bot@petry-projects>
…1045 part a) (#1047) The agent workflow_dispatch choice was hardcoded to [dev-lead], so manual evaluate/promote/rollback couldn't target the 6 #482 reusables now in the registry. List all 7 so they can be evaluated + promoted. (The gated SCHEDULED auto-promote — #1045 part b, decision A — remains for dev-lead.) Refs #1045, #1044. Co-authored-by: Claude Code Bot <bot@petry-projects>
…1045 part a) (#1047) The agent workflow_dispatch choice was hardcoded to [dev-lead], so manual evaluate/promote/rollback couldn't target the 6 #482 reusables now in the registry. List all 7 so they can be evaluated + promoted. (The gated SCHEDULED auto-promote — #1045 part b, decision A — remains for dev-lead.) Refs #1045, #1044. Co-authored-by: Claude Code Bot <bot@petry-projects>
…1045 part a) (#1047) The agent workflow_dispatch choice was hardcoded to [dev-lead], so manual evaluate/promote/rollback couldn't target the 6 #482 reusables now in the registry. List all 7 so they can be evaluated + promoted. (The gated SCHEDULED auto-promote — #1045 part b, decision A — remains for dev-lead.) Refs #1045, #1044. Co-authored-by: Claude Code Bot <bot@petry-projects>
…1045 part a) (#1047) The agent workflow_dispatch choice was hardcoded to [dev-lead], so manual evaluate/promote/rollback couldn't target the 6 #482 reusables now in the registry. List all 7 so they can be evaluated + promoted. (The gated SCHEDULED auto-promote — #1045 part b, decision A — remains for dev-lead.) Refs #1045, #1044. Co-authored-by: Claude Code Bot <bot@petry-projects>
…1045 part a) (#1047) The agent workflow_dispatch choice was hardcoded to [dev-lead], so manual evaluate/promote/rollback couldn't target the 6 #482 reusables now in the registry. List all 7 so they can be evaluated + promoted. (The gated SCHEDULED auto-promote — #1045 part b, decision A — remains for dev-lead.) Refs #1045, #1044. Co-authored-by: Claude Code Bot <bot@petry-projects>
…1045 part a) (#1047) The agent workflow_dispatch choice was hardcoded to [dev-lead], so manual evaluate/promote/rollback couldn't target the 6 #482 reusables now in the registry. List all 7 so they can be evaluated + promoted. (The gated SCHEDULED auto-promote — #1045 part b, decision A — remains for dev-lead.) Refs #1045, #1044. Co-authored-by: Claude Code Bot <bot@petry-projects>
…1045 part a) (#1047) The agent workflow_dispatch choice was hardcoded to [dev-lead], so manual evaluate/promote/rollback couldn't target the 6 #482 reusables now in the registry. List all 7 so they can be evaluated + promoted. (The gated SCHEDULED auto-promote — #1045 part b, decision A — remains for dev-lead.) Refs #1045, #1044. Co-authored-by: Claude Code Bot <bot@petry-projects>
…1045 part a) (#1047) The agent workflow_dispatch choice was hardcoded to [dev-lead], so manual evaluate/promote/rollback couldn't target the 6 #482 reusables now in the registry. List all 7 so they can be evaluated + promoted. (The gated SCHEDULED auto-promote — #1045 part b, decision A — remains for dev-lead.) Refs #1045, #1044. Co-authored-by: Claude Code Bot <bot@petry-projects>
…1045 part a) (#1047) The agent workflow_dispatch choice was hardcoded to [dev-lead], so manual evaluate/promote/rollback couldn't target the 6 #482 reusables now in the registry. List all 7 so they can be evaluated + promoted. (The gated SCHEDULED auto-promote — #1045 part b, decision A — remains for dev-lead.) Refs #1045, #1044. Co-authored-by: Claude Code Bot <bot@petry-projects>
…1045 part a) (#1047) The agent workflow_dispatch choice was hardcoded to [dev-lead], so manual evaluate/promote/rollback couldn't target the 6 #482 reusables now in the registry. List all 7 so they can be evaluated + promoted. (The gated SCHEDULED auto-promote — #1045 part b, decision A — remains for dev-lead.) Refs #1045, #1044. Co-authored-by: Claude Code Bot <bot@petry-projects>
…1045 part a) (#1047) The agent workflow_dispatch choice was hardcoded to [dev-lead], so manual evaluate/promote/rollback couldn't target the 6 #482 reusables now in the registry. List all 7 so they can be evaluated + promoted. (The gated SCHEDULED auto-promote — #1045 part b, decision A — remains for dev-lead.) Refs #1045, #1044. Co-authored-by: Claude Code Bot <bot@petry-projects>
…1045 part a) (#1047) The agent workflow_dispatch choice was hardcoded to [dev-lead], so manual evaluate/promote/rollback couldn't target the 6 #482 reusables now in the registry. List all 7 so they can be evaluated + promoted. (The gated SCHEDULED auto-promote — #1045 part b, decision A — remains for dev-lead.) Refs #1045, #1044. Co-authored-by: Claude Code Bot <bot@petry-projects>
…1045 part a) (#1047) The agent workflow_dispatch choice was hardcoded to [dev-lead], so manual evaluate/promote/rollback couldn't target the 6 #482 reusables now in the registry. List all 7 so they can be evaluated + promoted. (The gated SCHEDULED auto-promote — #1045 part b, decision A — remains for dev-lead.) Refs #1045, #1044. Co-authored-by: Claude Code Bot <bot@petry-projects>
…1045 part a) (#1047) The agent workflow_dispatch choice was hardcoded to [dev-lead], so manual evaluate/promote/rollback couldn't target the 6 #482 reusables now in the registry. List all 7 so they can be evaluated + promoted. (The gated SCHEDULED auto-promote — #1045 part b, decision A — remains for dev-lead.) Refs #1045, #1044. Co-authored-by: Claude Code Bot <bot@petry-projects>



Expands the
agentworkflow_dispatch choice from[dev-lead]to all 7 registry agents so manualevaluate/promote/rollbackcan target the 6 #482 reusables. Unblocks running the workflow to confirm promote-readiness. The gated scheduled auto-promote (#1045 part b, decision A) is still dev-lead's to build.Refs #1045, #1044.
🤖 Generated with Claude Code
Summary by CodeRabbit