Skip to content

fix: use effective default reviewers for bitbucket cloud#18467

Open
subnix wants to merge 3 commits intoWeblateOrg:mainfrom
subnix:patch-2
Open

fix: use effective default reviewers for bitbucket cloud#18467
subnix wants to merge 3 commits intoWeblateOrg:mainfrom
subnix:patch-2

Conversation

@subnix
Copy link

@subnix subnix commented Mar 13, 2026

Bitbucket Cloud has a hierarchical system of settings: workspace -> project -> repository. Some settings, like default reviewers, may be configured at a project level and inherited by a repository. Thus, we should use effective default reviewers to obtain reviewers for a pull request.

Bitbucket Cloud has a hierarchical system of settings: workspace -> project -> repository. Some settings, like default reviewers, may be configured at a project level and inherited by a repository. Thus, we should use [effective default reviewers](https://developer.atlassian.com/cloud/bitbucket/rest/api-group-pullrequests/#api-repositories-workspace-repo-slug-effective-default-reviewers-get) to obtain reviewers for a pull request.
@subnix subnix requested a review from nijel as a code owner March 13, 2026 15:29
@nijel nijel added this to the 5.17 milestone Mar 17, 2026
@nijel nijel self-assigned this Mar 17, 2026
@codecov
Copy link

codecov bot commented Mar 17, 2026

⚠️ JUnit XML file not found

The CLI was unable to find any JUnit XML files to upload.
For more help, visit our troubleshooting guide.

@nijel
Copy link
Member

nijel commented Mar 17, 2026

Can you please adjust tests to the changed behavior? Won't it break existing configurations?

@subnix
Copy link
Author

subnix commented Mar 18, 2026

Can you please adjust tests to the changed behavior?

Done

Won't it break existing configurations?

This change should be backward compatible since the required privileges remain the same, and default reviewers are only used for PR creation. I've tested this on a local instance and it works fine. Additionally, I've added some defensive code to safeguard against potential response parsing issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants