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

is it possible to run a rebase in a scriptrunner pre/post hook?

Hello All,

I was wondering if it were possible to run a custom rebase as part of a scriptrunner pre/post hook.

An example of what I am trying to accomplish.

If there are 4 commits being pushed, I want to run a rebase so that the end product is a single commit that contains all changes and the revisions of the other 3 are deleted so that they no longer exist in git's history.

I already know the git command that I would have to run for the actual rebase itself. I just need to know if it's possible to make all pull requests go through that rebase before being merged. Either via scriptrunner or some other method. The rebase would have to be run at any point between the user pushing up their changes and the pull request for those changes being merged back into master.

Any and all help is appreciated!


1 answer

Hi @Omar Morales ,

The ScriptRunner for Bitbucket team would advise against automating this functionality in a pre/post hook.

However, we do have a custom merge-check Script on our Library which can be used to enforce squashed commits before a Pull Request is allowed to be merged into the target branch.

This merge-check would then advise the user attempting the merge to squash their commits, which they would then need to do manually.

The custom merge-check can be found here:

If however, you do still want to automate squashing on Pull Request merge, an alternative would be to use Bitbucket's built-in merge strategies, as documented here:

Using Bitbucket's merge strategies, you can select to have all commits squashed on merge.

Kind regards,

Robert Giddings,

Product Manager, ScriptRunner for Bitbucket

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events