Hi there,
I'm building a pipeline that uses github flow, semantic-release and the usual conventional commits. On a merge to main, after a successful set of tests, semantic release does its job, commits the versioned artefacts, and includes `[skip ci]` in the commit message because why would we want another build.
This is where things start to go off a little. Given it's a tag, and not a commit, I would expect the tag to trigger a pipeline. However, it's clear that the tag is not triggering because of the `[skip ci]`.
Has anyone worked out a way, with semantic-release and Bitbucket, to tag commits, but also get the tags to trigger while ensuring that the tagged commit doesn't start another branch push build?
Cheers,
