PR for a forked repo automatically defaults to upstream in the original untracked repo and not the tracked fork remote.

Issue #17957 new
Cordell Barron
created an issue

Hello, I think this is a bug.

We have a forked a private repo and the codebase has diverged, However when a PR is created in the fork for merging with upstream, the PR automatically defaults to merge with develop branch of the original (untracked) repo. git remote -v with Repo2 correctly lists only Repo2 remote being tracked, and does not list Repo1 being tracked.


Repo1 is forked into a new repo called Repo2.
Changes made to Repo2 and then creating a PR to merge with Repo2/develop automatically defaults to Repo1/develop. It should be Repo2/develop.

This is confirmed as not intended since git remote -v correctly dipslays tracking for origin/Repo2 and not Repo1, yet it still defaults to Repo1 in the PR.

Comments (0)

  1. Log in to comment