Repository navigation
ci(docker): add workflow_dispatch + retrigger on own workflow edits - #867
Conversation
Hotfix #866 changed only the workflow file, so docker-publish did not retrigger and v2.11.0 was never re-published. Add workflow_dispatch and include the workflow file in the push path filter.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
LucasSantana-Dev has reached the 50-review limit for trial accounts. To continue receiving code reviews, upgrade your plan.
|
Failed to generate code suggestions for PR |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe Docker publish workflow now supports both automatic and manual triggering. A ChangesDocker Publish Workflow Triggers
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Suggested labels
🚥 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. Comment |
|



Follow-up to #866. The hotfix only touched
.github/workflows/docker-publish.yml, but that path was not in the workflow's own push trigger — so the workflow did not re-run and v2.11.0 was never re-published.Adds
workflow_dispatchand adds the workflow file itself to the push path filter so future workflow edits self-trigger.Summary by CodeRabbit