Currently build triggered by a push to master is cancelled by the build triggered by followup git tag on the same commit, due to github.ref being the same.
But we want master branch to deploy to :master docker tag, and git tags to be deployed to :lastest, so we need both builds to run.
To solve this, here I add github.ref_type (which can have values tag or branch) to the concurrency.group, such that tag- and branch-triggered builds don't cancel each other.
Currently build triggered by a push to master is cancelled by the build triggered by followup git tag on the same commit, due to
github.refbeing the same.But we want
masterbranch to deploy to:masterdocker tag, and git tags to be deployed to:lastest, so we need both builds to run.To solve this, here I add
github.ref_type(which can have valuestagorbranch) to theconcurrency.group, such that tag- and branch-triggered builds don't cancel each other.