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.
This PR creates a CD workflow that will build a new docker-image for every push to a
tag
(including the creation of a tag) in the form ofv1.2.3
.The images will be pushed to the github registry of this repository with the image tags taken from the git tag (i.e. for the major
1
, the major-minor1.2
, the major-minor-patch1.2.3
as well as thelatest
tag.The
Dockerfile
will by default build from themain
branch, which makes development easier in a docker-workflow. The CD however will always use the tag as build-arg.This is my first github-workflow (I did write many gitlab CI/CD pipelines). Information was taken from https://github.com/docker/build-push-action & https://github.com/docker/metadata-action
I did test this CD in my own fork: https://github.com/JayVii/ktistec/actions & https://github.com/JayVii/ktistec/tree/test_actions
I did testing builds (some with fake versions and some with proper) that have been pushed here: https://github.com/JayVii/ktistec/pkgs/container/ktistec