Push skaffold images only outside pull requests - #407
Conversation
The integration workflow calls the skaffold reusable workflow without a push input, so every pull-request run published multi-arch images to ghcr. Pin push to false there; the release workflow keeps the true default. Co-authored-by: Automata <automata@shikanime.studio> Signed-off-by: Shikanime Deva <william.phetsinorath@shikanime.studio> Change-Id: Idf12382be3522d1e1a915f189847a3ff6a6a6964
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe Skaffold integration job now disables image pushing when it calls the reusable Skaffold workflow. ChangesSkaffold integration
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to Pull-request Skaffold runs will build and render without publishing images, while release behavior remains unchanged. The change is ready to merge. Suggested reviewers: 🚥 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 |
What
Set
push: falseon the skaffold job that the integration workflow generates, so pull-request runs build and render without publishing images.Why
The integration workflow called the skaffold reusable workflow without a
with:block, so the reusable workflow'spushdefault (true) applied to every non-draft pull-request run: PR CI logged in to ghcr and pushed multi-arch images on each synchronize. Image publishing belongs to the release path, which keeps the default.References
Related: shikanime-labs/manifests#2215
Summary by CodeRabbit