Change default base repository for pull requests on forks #11729
Replies: 111 comments 68 replies
-
More discussion at https://github.community/t/changing-the-default-pr-target-when-creating-a-pr-from-a-fork/2842/2 |
Beta Was this translation helpful? Give feedback.
-
GitHub has a default branch setting. The page says:
Unless I am missing something, that setting is not respected for PRs on a fork, given that the default branch of the upstream repo seems to be taken as the base branch for the PR. How about adding a
When creating a PR, these settings could be used to give the current behavior. Then users could change the settings to fit their needs. I'd be happy to learn about any implications I might be missing 😁 |
Beta Was this translation helpful? Give feedback.
-
Has anyone got an update on how to change the base repo? |
Beta Was this translation helpful? Give feedback.
-
To change this behaviour you'd have to change the Compare page URL by external add-ons.
I'm talking a green pull request button. |
Beta Was this translation helpful? Give feedback.
-
The current developer experience is really hard to work with -- I've incorrectly opened (and then closed) PRs to upstream several times at this point and I'm going to have to just remove my upstream association which is a real shame. Would love a solution to this for future projects! |
Beta Was this translation helpful? Give feedback.
-
Same problem here! Just today I closed a PR just clicks before merging it to master on the wrong repository. |
Beta Was this translation helpful? Give feedback.
-
I can attest - this is very annoying. |
Beta Was this translation helpful? Give feedback.
-
same experience here. My solution was finally to create fork form the fork: |
Beta Was this translation helpful? Give feedback.
-
The output of |
Beta Was this translation helpful? Give feedback.
-
Why is this not a setting? One of the main use cases for Forking a repository is to take over a project that is out of maintenance - where the previous owner is ignoring all PRs. Please @github-staff consider just making it a setting so we don't have to click 3 times on every PR to avoid accidentally PR'ing the fork. Thanks. |
Beta Was this translation helpful? Give feedback.
-
This behavior is so frustrating. As a workaround, to detach a repository you can request a ticket here: https://support.github.com/contact?tags=rr-forks&subject=Detach%20Fork&flow=detach_fork |
Beta Was this translation helpful? Give feedback.
-
Please provide this setting. |
Beta Was this translation helpful? Give feedback.
-
Same situation here, we want to work mainly in our fork and contribute some PRs upstream, so we don't want to detach. We had some accidental PRs already, and it's embarrassing. Please let us configure the default |
Beta Was this translation helpful? Give feedback.
-
I have a website template that people fork to use, and the github.com UI for pull requests defaulting to the upstream repo instead of the base repo has caused so many people (including me!) to open accidental PRs (against the template itself instead of their own main branch) that I had to create a label specifically for it: |
Beta Was this translation helpful? Give feedback.
-
This starts to suck. The thread is over a year old and as far as I could see has gotten no reaction from GitHub. There are two aspects to this that make this very annoying: first, it's bothering lots of people and second, as I pointed out in my earlier post, this should be relatively easy to fix. One option to potentially get some traction with this, is for someone with an appropriate account type (Pro, Enterprise etc.) to open a support ticket and point this out. I've had success doing that with Atlassian but I only have a free GitHub account myself. |
Beta Was this translation helpful? Give feedback.
-
Same here! |
Beta Was this translation helpful? Give feedback.
-
+1 super annoying. I am even writing a userscript for it until github gets it together. |
Beta Was this translation helpful? Give feedback.
-
Just want to chime in, this also has bitten me several times. Please add this setting! |
Beta Was this translation helpful? Give feedback.
-
+1 because I felt dumb for even looking it up after not finding the setting in the repo setting, and it turns out it was never an option! :O |
Beta Was this translation helpful? Give feedback.
-
+1 how is this not a thing? |
Beta Was this translation helpful? Give feedback.
-
+1 Impacting my team, too. This is very counter-intuitive behavior. |
Beta Was this translation helpful? Give feedback.
-
Running into this issue as well, would love the option to select a default base branch for forks. As others mentioned, If the upstream repo is archived could that maybe a way to enable this automatically at least without needing a config option? |
Beta Was this translation helpful? Give feedback.
-
In my opinion, it is a bug that GitHub chooses the original repo as default upstream instead of the own (forked) repo – even if the original one is not archived.
|
Beta Was this translation helpful? Give feedback.
-
Just created accidental PR in upstream repository. I would really like to be able to prevent myself from doing the same another time by accident. |
Beta Was this translation helpful? Give feedback.
-
+1 this needs to be a priority. Surprised it still isn't an option |
Beta Was this translation helpful? Give feedback.
-
Here is a really solid workaround I've been using for a while. Instead of creating your PR from the web, create it from the command line, like so:
(Of course you'll need to install the Background |
Beta Was this translation helpful? Give feedback.
-
just here to throw another log on the fires of annoyance that are so well explained by previous commenters |
Beta Was this translation helpful? Give feedback.
-
I have miraculously managed not to open a wrong PR so far, but the same useless clicks every time annoy me nonetheless. |
Beta Was this translation helpful? Give feedback.
-
It seems absurd that in 2024, GitHub still can't handle the basic feature of setting a default base repository for pull requests. This oversight surely causes constant frustration and increases the risk of errors in many teams. How can such a fundamental functionality be missing from a platform as advanced as GitHub? |
Beta Was this translation helpful? Give feedback.
-
I've forked a repository which has been archived by the owner, so there won't be any prs accepted to the original repository.
Therefore I'd like to change the base repository for all PRs made from to my repository but this seems not possible.
Is there a recommended way to deal with this situation other than (re)creating the repository without forking?
Thanks a lot!
Beta Was this translation helpful? Give feedback.
All reactions