Why is bitbucket not automatically updating my pull request?

Question

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.

@Downvoter: What's wrong with my question? – Andrew Grimm Oct 12 '15 at 22:29 — Andrew Grimm, Oct 12 '15 at 22:29

score 1 · Answer 1 · answered Jun 04 '21 at 01:59

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

score 0 · Answer 2 · answered Oct 13 '15 at 04:59

0

Try and make sure that:

upstream is up-to-date (git fetch upstream, with upstream being a remote referencing the original repo)
your PR branch is rebased on top of upstream/master (with potential merge conflict resolution)

Then try a git push --forceand see if the PR update takes place or not.

answered Oct 13 '15 at 04:59

VonC

1,262,500
529
4,410
5,250

As a heads up, in my situation, there's only a single central repo, plus various developers' machines. – Andrew Grimm Oct 13 '15 at 10:27
@AndrewGrimm PR means there is a fork involved, no? – VonC Oct 13 '15 at 12:46
@VonC no it does not. – airtonix Jun 04 '21 at 01:57
@air 6 years later, I agree: It does not. – VonC Jun 04 '21 at 04:47

Why is bitbucket not automatically updating my pull request?

2 Answers2