Docker: improve tagging, distinguish main and latest
#1891
Merged
Conversation
This file contains 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
github-actions
bot
added
the
gh-actions
✅ Deploy Preview for conkyweb canceled.
|
brndnmtthws
force-pushed
the
docker-image-tagging
branch
3 times, most recently
from
542a7a2
to
19a7d7b
Compare
* Use `latest` for the latest release * Use `main` (or the branch) for the latest dev builds against a branch * Tag releases with their version * Only push when building against `main` branch * Only build amd64 images on PRs for speedier builds * Separate main/PR caches
brndnmtthws
force-pushed
the
docker-image-tagging
branch
from
0169c5e
to
ebe09b6
Compare
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.
latestfor the latest releasemain(or the branch) for the latest dev builds against a branchmainbranch