On Bitbucket server, when a PR is opened from one repo into another and the branch on the source repo does not exist on the destination repo, PR Decoration fails to be displayed with the error message:"An error occurred while getting data from Sonarno ref found for <Branch_Name>"For clarification, our typical workflow goes something like this:Create your own fork of the main repoIn your fork, create your development branch and do your workPR from your dev branch to the master branch of the main repoI've been through every setting I can think of and I'm just not seeing what I'm doing wrong here that it's referencing the branch name from the source branch (fork dev branch; test-23 in this case) and failing when it doesn't exist. If I just create a branch with the same name, it works, but I shouldn't have to push my dev branches from my fork into the main repo to get this to work. What am I missing here?

Community
Products
Apps & Integrations
Questions
Sonar for Bitbucket PR decoration fails with cross-repo PRs

Sonar for Bitbucket PR decoration fails with cross-repo PRs

On Bitbucket server, when a PR is opened from one repo into another and the branch on the source repo does not exist on the destination repo, PR Decoration fails to be displayed with the error message:

"An error occurred while getting data from Sonar
no ref found for <Branch_Name>"

For clarification, our typical workflow goes something like this:

Create your own fork of the main repo
In your fork, create your development branch and do your work
PR from your dev branch to the master branch of the main repo

I've been through every setting I can think of and I'm just not seeing what I'm doing wrong here that it's referencing the branch name from the source branch (fork dev branch; test-23 in this case) and failing when it doesn't exist. If I just create a branch with the same name, it works, but I shouldn't have to push my dev branches from my fork into the main repo to get this to work.

What am I missing here?

1 answer

1 accepted

0 votes

Answer accepted

Hi,

This is a known issue with app versions 2.6.x where the branch information is pulled from the target instead of the source repository when using forks. We will deploy a fix later today. I'll reply back here when it is available.

Thanks for your understanding.

Best regards,
Michael (app vendor)