Greetings,
I have a slight annoyance and just wondering if this is intended behavior.
I have forked a repo which we use as a submodule in another project.
The fork went fine and the codebases have now diverged as expected, however everytime I create a PR of the 'forked' repo for a merge into the project (not the original repo that I forked) bb automatically sets the branch to push as that of the original repo that I forked...
e.g.
Repo1 was forked and called Repo2. Repo2 is now a submodule of Repo3.
When I do some work in Repo2 and create a PR, I would expect it to merge into Repo2, however bb automatically sets the target branch to one in Repo1.
It's not a show stopper since I just have to change the drop down to the correct repo, however it recently resulted in a number of declined PR's when I realised it was going to the wrong place (i.e it was going to go upstream?).
Is this intended behavoir? When I git remote -v on the forked repo (i.e Repo2) it does not list the original repo (Repo1, as expected), but the PR still seems to (by default) want to go to Repo1 (and not Repo2, which is what I expect).
Cheers,
Cordell
