You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I've set up repository change direction on a job with the following regular expression match:
Exclude changesets:
.*\[skip[ -]ci\].*
When I push a commit with a single line commit message like this:
chore(build): this is a build to skip [skip ci]
The commit is ignored, as expected. However, if I push a commit with a multiline commit message:
chore(build): this is a multi-line message [skip ci]
this should not build but it does
The change is detected and a build triggered.
What's the correct regular expression to detect [skip-ci] correctly even when there are multiple lines of text in the commit message?
Hi Scott,
Thanks for your question!
I hope the below will answer your question:
.*\[skip[ -]ci\].*((.|\n)*)
This will include 'n' number of lines.
Thanks,
Robhit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.