fix(ci): restore Docker build workflow#24
Conversation
The docker.yml workflow was dropped during the Gleam rewrite (it replaced the entire Elixir codebase). The Dockerfile survived, but without this workflow no images are built/published to GHCR — and the live deployment on feedreader-2 uses ghcr.io/kasuboski/feedreader:main. Restored with SHA-pinned actions, persist-credentials: false, and a concurrency group.
|
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 (1)
📜 Recent review details⏰ Context from checks skipped due to timeout. (1)
🔇 Additional comments (1)
📝 WalkthroughWalkthroughA new GitHub Actions workflow file is added that triggers on branch pushes and ChangesDocker multi-arch build and publish workflow
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes Possibly related PRs
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. Comment |
What
The
docker.ymlworkflow was dropped during the Gleam rewrite (PR #23 replaced the entire Elixir codebase). The Dockerfile survived, but without this workflow no images are built/published to GHCR — and the live deployment on feedreader-2 usesghcr.io/kasuboski/feedreader:main.Changes
Restored the Docker build workflow with:
persist-credentials: falseon checkoutcancel-in-progress: trueVerification
Summary by CodeRabbit