nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Difference of refs/pull-requests/<ID>/merge and refs/pull-requests/<ID>/from

qian-jin

When a pull request created, I saw following remote branch created automatically,

refs/pull-requests/<ID>/merge
refs/pull-requests/<ID>/from

What is the difference of these two?

BTW, I am trying to polling git to check new pull requests and automatically test them (I have no permission to change to Bitbucket server's setting to add a pull request notification plugin).

Accepted answers

Isabella Stephens

Hi,

First I want to point out that this is an internal implementation detail, and not part of our API. Anything you build that depends on these files may stop working after an upgrade to Bitbucket Server without warning. A better alternative may be to talk to your System Administrator about installing a plugin.

To answer your question, the "from" ref points to the head of the source branch of the PR. The "merge" ref points to a merge commit between the "from" ref and the head of the target branch. To understand why we track these it might help to read this blog post.

You should note that these refs are not automatically updated when a change is made to the branch. A user must view the PR in their browser for the refs to be updated. You can read this answer to understand why. You cannot rely on these refs being updated in order to pick up changes to the pull request as they happen.

Another option may be to look at our REST API - you can use this endpoint to retrieve all pull requests in a repository. From there, fromRef.latestCommit for each PR in the response will tell you the commit at the head of the source branch, similar to the "from" ref, except the value from the REST API will update automatically.

Hopefully this helps clarify things.

Cheers,

Isabella - Atlassian

All comments

Isabella Stephens

Hi,

Hopefully this helps clarify things.

Cheers,

Isabella - Atlassian

qian-jin

Thank you very much! It is very helpful.

unknown

Hi,

If "pull-request/*/merge" is an internal API that might break at any time, what would be the proper supported way to implement the solution suggested here https://stackoverflow.com/a/32073284/1788881 in order to test the merged code instead of the source branch during PR builds?

Todd Boyd_usdn4w

You suggest using a plugin, but every plugin I've found for BitBucket and Jenkins integration just uses the internal API, not the REST API. They all broke on me just now, so I'm scrambling to figure out how to get pull requests built automatically.

Todd Boyd_usdn4w

We have been using the Stash Pull Request Builder plugin in Jenkins, which provides variables to build a URL for the destination repository and the source of the pull request which are configured as two separate repository references. We then do a local merge from the source into the destination during the PR build.

Way more complicated than it used to be, but it does work. YMMV on other build services.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

bitbucket

bitbucket-server