-
Suggestion
-
Resolution: Won't Fix
Bitbucket attempts to auto-merge pull requests that were merged locally via a rebase. It would be great if Bitbucket could detect more unique workflows and situations where rebasing may cause the pull request to lose track of the commits or branches. Or detect when a user has rebased and merged, then removed the branch that the pull request was the source/destination of.
[BCLOUD-6768] Detect and handle rebasing and auto-merge in more situations
Remote Link | Original: This issue links to "Page (Confluence)" [ 664388 ] |
Resolution | New: Won't Fix [ 2 ] | |
Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
Remote Link | New: This issue links to "Page (Confluence)" [ 664388 ] |
Component/s | New: Pull Request - Merge / Checks [ 66495 ] |
Workflow | Original: JAC Suggestion Workflow [ 3532471 ] | New: JAC Suggestion Workflow 3 [ 3598097 ] |