PR-Booster For Bitbucket

Bitbucket 10.x compatibility

Two fixes:

1.) Fix severe regression in v2025.05.09: Rebase / Squash / Amend buttons doing nothing (seem to freeze and say “Squashing…” and never complete).

2.) Fix to ensure compatibility with "Draft Mode" pull-requests: when users created pull-requests in “Draft Mode”, the Rebase / Squash / Amend buttons would disappear. Fixed!

Fix to ensure compatibility with "Draft Mode" pull-requests:

When users created pull-requests in “Draft Mode”, the Rebase / Squash / Amend buttons would disappear. Fixed!

Bug fix for issue #577 - approvals withdrawn when PR re-opened.

https://bitbucket.org/gsylviedavies/pr-booster-for-bitbucket/issues/577

Revert & Cherry-Pick stopped allowing the "[x] - Create pull request?" option due to some JavaScript incompatibility with newer Bitbucket versions, making this feature useless for many customers. Fixed!

We've also finally fully implemented dark-mode compatibility for PR-Booster.

Bitbucket 9.x Compatibility

Bitbucket 9.x Compatibility

Fixed bug: the small "parent commit" popup button on the commit drilldown page was broken (clicking on it did nothing). The way PR-Booster created its "Cherry-Pick" and "Revert" buttons was breaking a small part of Bitbucket's native web UI on that page. Fixed!

Fixed bug: the small "parent commit" popup button on the commit drilldown page was broken (clicking on it did nothing). The way PR-Booster created its "Cherry-Pick" and "Revert" buttons was breaking a small part of Bitbucket's native web UI on that page. Fixed!

Fixed issue #532:

Clicking on the “rebase --autosquash” button can cause loss of commits if the rebase process encounters a merge conflict.

Fixed issue #532:

Clicking on the “rebase --autosquash” button can cause loss of commits if the rebase process encounters a merge conflict.

One fix:

• Erroneously grayed out Rebase/Squash/Amend buttons in fork scenario (issue #191)

One fix:

• Erroneously grayed out Rebase/Squash/Amend buttons in fork scenario (issue #191)

Some customers have been recently reporting issues with the disapproval-retention and auto-drop-approvals feature (seems the logic is not firing?). This version includes some improvements to the logic as well as significant improvements to tracing/debugging capabilities around these features.

Some customers have been recently reporting issues with the disapproval-retention and auto-drop-approvals feature (seems the logic is not firing?). This version includes some improvements to the logic as well as significant improvements to tracing/debugging capabilities around these features.

Bug fix: Revert/Cherry-Pick broken on Bitbucket 7.21.15+, 8.9.4+, and 8.13+.

A JSON parsing library we were depending on is no longer included in those versions of Bitbucket. This removal broke our Revert and Cherry-Pick feature.

Fixed !

Bug fix: Revert/Cherry-Pick broken on Bitbucket 7.21.15+, 8.9.4+, and 8.13+.

A JSON parsing library we were depending on is no longer included in those versions of Bitbucket. This removal broke our Revert and Cherry-Pick feature.

Fixed !

• Fix bug with revert button.

• Fix bug with revert button

• New feature: brought back the "autosquash" option for the Rebase button.
• One bugfix: cherry-pick now correctly sets the AUTHOR and COMMITTER metadata.

Background information: porting the Rebase / Squash / Amend logic to support Bitbucket 8.x was a huge job we completed a year ago. During that work we realized we did not know how to port the "autosquash" variation of rebase and needed to do more research to support that. That work is finally complete and ready now. Sorry it took so long!

P.S. - WE HAVE BIG NEWS: WE NOW OFFER A BITBUCKET CLOUD VERSION OF THIS APP (PR-BOOSTER)! EMAIL US AT support@bit-booster.com TO LEARN MORE !

Version v2023.08.16 contains one new(ish) feature, and one bug fix:

• New feature: brought back the "autosquash" option for the Rebase button.
• One bugfix: cherry-pick now correctly sets the AUTHOR and COMMITTER metadata.

Background information: porting the Rebase / Squash / Amend logic to support Bitbucket 8.x was a huge job we completed a year ago. During that work we realized we did not know how to port the "autosquash" variation of rebase and needed to do more research to support that. That work is finally complete and ready now. Sorry it took so long!

P.S. - WE HAVE BIG NEWS: WE NOW OFFER A BITBUCKET CLOUD VERSION OF THIS APP (PR-BOOSTER)! EMAIL US AT support@bit-booster.com TO LEARN MORE !

Bugfix for cherry-pick / revert:

• The "create cherry-pick via pull-request" feature was broken. Fixed !

Bugfix for cherry-pick / revert:

• The "create cherry-pick via pull-request" feature was broken. Fixed !

Fixed permission bug in Rebase/Squash/Amend logic when PR spans fork. The buttons were correctly greyed out if the user did not have write permission to the "from" repository, but for the wrong reason:

PR-Booster canRebase() logic failed: com.atlassian.bitbucket.AuthorisationException: You are not permitted to access this resource

Version v2023.01.18 fixes the logic so that now PR-Booster correctly detects that write permission is not present, and greys out the buttons with that reason, instead of greying them out because an exception was tripped.

Fixed permission bug in Rebase/Squash/Amend logic when PR spans fork. The buttons were correctly greyed out if the user did not have write permission to the "from" repository, but for the wrong reason:

PR-Booster canRebase() logic failed: com.atlassian.bitbucket.AuthorisationException: You are not permitted to access this resource

Version v2023.01.18 fixes the logic so that now PR-Booster correctly detects that write permission is not present, and greys out the buttons with that reason, instead of greying them out because an exception was tripped.

Sometimes the rebase button would report back "stale data, cannot rebase", and users would need to refresh the pull-request screen as a workaround. Fixed!

Sometimes the rebase button would report back "stale data, cannot rebase", and users would need to refresh the pull-request screen as a workaround. Fixed!