Earn badges and make progress
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
Participate in fun challenges
Challenges come and go, but your rewards stay with you. Do more to earn more!
Gift kudos to your peers
What goes around comes around! Share the love by gifting kudos to your peers.
Rise up in the ranks
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
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.
Automation trigger: 'Commit Created' does not account for merge commits
Edited
I am setting up some automation rules to capture {{commit.hash}} for every commit created using the 'When Commit Created' trigger. The rules does get triggered when I make a commit to my dev branch (b458626). After merging to the 'main' branch, this merge commit does NOT trigger the rule (a1ed54d). Is the rule making a distinction between a commit and a merge commit?
1 answer
I checked out their docs, and they don't mention if they differentiate between "regular" and "merge" commits, so I would assume the same like you did. But, it seems it is not how it is... :-/
Funnily, we develop the DevOps Automation app for self-hosted Jira, and our Commit Created trigger works as you wrote: we provide a {{devops.commit.isMerge}} smart value which you can use to filter merge commits:
You confirmed that it is an intuitive design. :-)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.