Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Should [skip ci] stop a tag trigger?


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?



1 answer

0 votes
Ben Atlassian Team Aug 30, 2022

Hey Andrew,

Welcome to the Bitbucket Cloud community! :)

The current behavior of [skip ci] means that every type of trigger for builds will be ignored, this includes commits to branches, pushing tags, and performing PR's.

I have raised a feature request ticket for our developers on your behalf, feel free to "Watch" this for future updates and "Vote" to increase the visibility of customer demand:


- Ben (Bitbucket Cloud Support)

Suggest an answer

Log in or Sign up to answer
Site Admin
Community showcase
Published in Bitbucket

Git push size limits are coming to Bitbucket Cloud starting April 4th, 2022

Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...

3,486 views 3 10
Read article

Atlassian Community Events