So there's this org which has a certain highly regulated Bitbucket repo R in a centrally-governed project C. We maintain a synchronized fork of C/R, T/R, in our own Bitbucket project T. To make a change, we have to
- create a branch T/R:feature-branch
- push a change to it
- submit a PR from T/R:feature-branch to C/R:master and get an approval from the governance team for C.
This situation has led on more than one occasion to certain changes submitted by different subteams interfering with other subteams of T. To try and prevent this problem, I want to impose the restriction that all cross-fork PRs and merges into C/R come from a specifically designated master-like branch in T/R, so that the dev branches are serialized onto that branch and undergo local reviews before we "throw them over the wall".
Given that we have no control over the permissions or settings of C or C/R, what options do I have to enforce that cross-fork PRs may only come from T/R:local-master branch?