rebase resets "minimum successful builds" counter

rebase / squash / amend or even regular old "git merge master; git push" resets the "minimum successful builds" counter, blocking merges when this feature of Bitbucket is enabled.

The problem is that rebase / squash / amend change the commit-id (rewrite history), but "minimum successful builds" assumes the commit-id will never change.

It's not a bug in Bit-Booster, but maybe we can fix it to make "minimum successful builds" aware of "patch-id" just like we did with the PR we filed against the free Auto Unapprove add-on.

Comments (1)