Menu
After pushing to a branch that's the subject of a pull request, I'm getting the message
There are new commits not included in this pull request. Update now.
Why am I getting this, rather than the pull request being automatically updated?
The only difference between this pull request and other ones I've made with bitbucket is that this one involved a merge conflict, which I've since resolved. Does that play a role?
I tried searching for the error message, and only came across other people with the same question.
904
To update by rebasing, click the drop down menu next to the Update Branch button, click Update with rebase, and then click Rebase branch. Previously, Update branch performed a traditional merge that always resulted in a merge commit in your pull request branch.
Cause. Cause#1: The pull request is not up to date with the tip of the source branch, or the tip of the target branch.
Late to the table, but in short it's because Bitbucket Web UI knows about changes in the repo stored on the bitbucket infrastructure due to the git hooks it installs.
In some cases these become corrupted and rage ensues.
I've found the easiest way to deal with this is close your PR and re-open a new one. :s
source: https://confluence.atlassian.com/bitbucketserverkb/pull-requests-not-reflecting-changes-pushed-to-remote-branch-779171762.html
191
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
