The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Special pull-requests/* branches - is it default behavior?

Maksym Grebenets
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 23, 2016

Hi

You know how Bitbucket Server automatically creates special pull-requests/* branches for pull requests.

So my question is whether this is a default behavior for BB or is it configurable somewhere during installation?

We are looking into adopting Sonar plugin for BB. This plugin, however, for all pull requests  uses the name of the source branch for integration. So we never get a proper integration for pull-requests/* branches.

The plugin developers are also asking if this is default BB behavior or not: https://mibexsoftware.atlassian.net/browse/SONAR-89

 

I suppose this is the default, since there can be multiple pull requests open from the same branch.
 

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
James Dengel
Contributor
November 11, 2016

The behaviour is as you expect.

refs/pull-requests/$(pull-request-id)

 

This is where the cross repo pull requests are stored. I have not found any configuration.

TAGS
AUG Leaders

Atlassian Community Events