ci: register conductor in create-tag + release workflows - #61
Conversation
Adds the conductor worker (merged in #59) to the Create Tag workflow's choice list and to the Release workflow's tag-push trigger so `gh workflow run create-tag.yml -f worker=conductor` works and `conductor/v*` tags fire the release dispatcher. Both lists kept alphabetical between coding and eval.
|
Caution Review failedPull request was closed or merged during review No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughGitHub Actions workflow configurations updated to include the conductor module in tag creation and release triggers. The create-tag workflow now allows manual selection of conductor for version bumping, and the release workflow triggers on conductor version tag pushes. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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. Review rate limit: 0/1 reviews remaining, refill in 60 minutes.Comment |
Summary
Follow-up to #59 (conductor worker merged). Register conductor with the two workflows that hardcode the worker list:
Both lists kept alphabetical between `coding` and `eval`.
After merge
(The version bumps from 0.1.0 → 0.1.1 because Create Tag always increments. Initial register is fine at 0.1.1.)
Test plan
Summary by CodeRabbit