Add CI workflow to verify Docker build - #180
Open
Mustaphayinka wants to merge 3 commits into
Open
Conversation
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #178, the build verification part.
This adds a GitHub Actions workflow to build the project’s Dockerfile whenever a push or pull request changes either the Dockerfile or the workflow itself. It is meant to catch build breakage early, as requested.
It covers only the “building the Docker image” part of the issue. It does not include publishing or deployment to Docker Hub, GHCR, or any other location. That work requires registry credentials and a maintainer’s decision about where the images should live, so I’ve left it out for now. I can take it on in a follow-up PR if that would be useful.
It uses docker/build-push-action with push set to false, meaning it only builds and verifies the image; nothing is pushed anywhere. I added GitHub Actions layer caching with type=gha as well, which keeps repeated runs fast. The workflow triggers only when the Dockerfile or this workflow file changes, rather than running on every unrelated commit.