Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

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.

Deleted user Avatar
Deleted user

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.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Use Adaptavist for Bitbucket Server merge check to see if all commits from branch are in another

I am wondering if there is a way to use Adaptavist Script runner for Bitbucket server to see if all commits from one branch are in another branch. For example, consider the following branches.

- master

- development

- feature/1234-abc- feature


I would like to check if the commits from feature/1234-abc feature are in development prior to the merge into master from feature/1234-abc. I know that I can find the to branch using this 

mergeRequest.pullRequest.toRef.displayId == "master"


But I couldn't figure out how to compare the commits, I was trying to rework the example of merge commits detected on feature branch, but was unsuccessful.


1 answer

Hi @Richard W 

We have recently released the Enforce Gitflow Workflow script for scriptrunner, and I believe it should help you achieve what you need to do.

Even if you are not using the Gitflow workflow, you could have a look at the script and specifically the way it checks that a commit from one branch exists in another one.

Just to add, you do not need to compare more than one commits, you just need the latest one, as its id depends on the previous commits.



Suggest an answer

Log in or Sign up to answer

Atlassian Community Events