[minor] optimize docker pulls when action is executed #74
+116
−53
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.
When a docker-based github-action is run in a workflow, github pulls the repo and then builds an image from the
Dockerfile
every time. In our case this involves downloading and installing some apk packages. We can pre-bake this image and save some bandwidth and time.release
job out of theci.yaml
workflow and into a newrelease.yaml
GHA workflow. Release runs only on main merges.Dockerfile.base
contains all of the apk dependencies. It creates the runtime imageDockerfile.base
and pushes toghcr.io/planetscale/ghcommit-action:v${new_version}
. autotag is still used to calculate the $new_version.Dockerfile
and commits back to the main branch.The runtime
Dockerfile
is now a 1-liner referencingghcr.io/planetscale/ghcommit-action:v${new_version}'