Repository navigation
ci: drop Docker build/push job from deploy workflow - #73
Conversation
Deployment target is Vercel, and nothing consumes the adamgaborjaniszabo/debate-trainer image anymore, so the docker job and the production-assets artifact handoff that only fed it are dead weight. Keeps the quality, database-tests, and browser-tests gates.
There was a problem hiding this comment.
Programcode has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Free Run ID: 📒 Files selected for processing (1)
💤 Files with no reviewable changes (1)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe deployment workflow no longer uploads production assets as an artifact or runs the Docker job that built and pushed multi-architecture images. ChangesDeployment workflow
Estimated code review effort: 2 (Simple) | ~8 minutes Note 🎁 Summarized by CodeRabbit FreeYour organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Essentials by visiting https://app.coderabbit.ai/settings/billing. Comment |
Deployment target is Vercel now and nothing consumes the
adamgaborjaniszabo/debate-trainerimage anymore (verified: no references on the VPS), so thedockerjob and theproduction-assetsartifact handoff that only fed it are removed.Keeps the
quality,database-tests, andbrowser-testsgates untouched. Workflow name intentionally left as-is:staging-e2e.ymltriggers on it viaworkflow_run.Summary by CodeRabbit