Change default base repository for pull requests on forks #11729
Replies: 140 comments 94 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 maintain a website template that people fork to use. The fact that the github UI for pull requests defaults 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 (22 and counting): |
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.
-
I have a free account so I can't open a ticket but I just to be counted amongst those requiring to be able to set a base branch. I usually used BitBucket and it doesn't have this behaviour. I've also ended up unintentionally creating PRs against the upstream repo. |
Beta Was this translation helpful? Give feedback.
-
How is this not a thing already? Seriously. |
Beta Was this translation helpful? Give feedback.
-
Would really like to start working with forks ... but thanks to GitHub we cannot. :/ |
Beta Was this translation helpful? Give feedback.
-
Just made a mistake a little while ago because I'm a dummy and assumed that the PR would go to my fork's main branch. Now I've got a closed PR on the base repo, haunting and mocking me because I can't read. @jsoref solution of forking the fork makes sense, but tbh that's a stupid solution for something that should be a setting. |
Beta Was this translation helpful? Give feedback.
-
One more on this. Accidental PRs are very annoying on all ends. How is this not fixed yet after 2.5 years? |
Beta Was this translation helpful? Give feedback.
-
I'd also like a change on the vein of usirg's suggestion. |
Beta Was this translation helpful? Give feedback.
-
Just made an accidental PR myself targeting the upstream repository instead of the |
Beta Was this translation helpful? Give feedback.
-
+1 please fix this |
Beta Was this translation helpful? Give feedback.
-
+1 here too |
Beta Was this translation helpful? Give feedback.
-
We have the same problem, please offer a solution @github |
Beta Was this translation helpful? Give feedback.
-
+1 here too |
Beta Was this translation helpful? Give feedback.
-
Another +1... |
Beta Was this translation helpful? Give feedback.
-
+1 on this, made this mistake for the second time in as many weeks today. I hope my PRs (both of which were open for less than a minute before I closed them) don't bother the upstream maintainers, they do great work and the last thing I want is to distract them or slow them down... but I move fast and this default setting is awful. |
Beta Was this translation helpful? Give feedback.
-
+1 |
Beta Was this translation helpful? Give feedback.
-
+1. |
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