Add both version tag and branch name tag
See original GitHub issueI have the following configuration:
type=raw,value={{branch}}
type=sha
type=semver,pattern={{version}}
But when I push just a tag to the main branch, the container is tagged only with latest
, 1.0.0
and sha
tags, but not with the branch name.
Is it possible to always have a branch name tag in addition to version tag? The goal is to be able to refer either to a specific version tag or the latest container build in each branch.
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (1 by maintainers)
Top Results From Across the Web
Git - Tagging - Git SCM
Git supports two types of tags: lightweight and annotated. A lightweight tag is very much like a branch that doesn't change — it's...
Read more >Is it possible to have version tags on multiple branches in git?
1 Answer 1 · Actually, tag names do work a lot like branch names in Git. The issue here is that branch names...
Read more >git tag | Atlassian Git Tutorial
Git tag command is the primary driver of tag: creation, modification and deletion. Learn how you can use them to organize code and...
Read more >Fixing GIT Branch and Tag Name Collisions - Geedew
You should never name a tag and a branch the same name! It makes sense in a case like this to use naming...
Read more >Branch and tag with same name cause multiple problems
Pushing a branch with the same name as a tag causes multiple problems throughout the GitLab application. I will list them here, and...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ok, it worked after I added a couple of tweaks.
Thanks a lot! I’ll test the workaround in a couple of days.
And yes, a global expression would be nice: https://github.com/docker/metadata-action/issues/102#issuecomment-859083282