Our current pipeline commits back to master with a [ci skip] added to the message when it's just adding to the changelog etc,
Subsequently if a dev, working on a branch merges up from master the automatically created commit message in sourceTree (though not when merged in the bitbucket web interface) will include all merged commit messages by default which may include the ci skip flag.
Is there a way to configure sourceTree to automatically remove these flags on a merge commit so pipelines will get run?
Hi Robin! At the moment it's not possible to automate that kind of action. You can do it manually by using the 'Amend latest commit' option located at the bottom left of the commit window. Alternatively, if you're okay with using the command line, you could write a script to automate this.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs