![github desktop fork update github desktop fork update](https://i.stack.imgur.com/GmsTH.png)
You have to open the fork of the repo manually in the app. When you click "Open this pull request in Desktop," on a pull request page, Desktop attempts to clone the upstream repo, or opens the upstream repo if it already exists. Update: Solution for this shipped to production in 2.4 □ □
![github desktop fork update github desktop fork update](https://www.classicpress.net/wp-content/uploads/2020/02/step1-fork7.png)
Problem 5: Cannot open a pull request from a PR page in your fork in Desktop ( issue here) So we're going to show those, and it's just important to make clear to people that that's what they're seeing. If you fork a repo and make a PR to contribute to the upstream repo, there's currently no way to view your PR in Desktop from your fork because the PR is associated with the upstream repo, not your fork of it.Īfter further consideration, we think that in nearly all cases, if you're working on a fork in Desktop you care most about the PRs targeting the parent repository. Update: Solution for this shipped in 2.4! □ □ A potential path forward on that specifically is described here: #6875 (comment) Problem 4: Viewing pull requests for the upstream repo from your fork (including your own PR) ( issue here) We also have an existing feature (notification when diverging from default branch) that was intended to solve some of this, but it's currently not working as designed. One way in which this manifests is when you're creating a new branch, and if there has been new work on the upstream repo, you're starting your branch out-of-date, described here by #7762 You don't necessarily know they exist, and even if you do it's not clear for people who don't do it frequently how to merge in those changes to get your branch up to date. It's not at all straightforward how to pull in updates from the default branch of the upstream repo while you're working on a contributions on your forked repo. Update: A partial solution to this, scoped only to when creating new branches, shipped in 2.4! □ □ Problem 3: Staying up to date on your fork with changes on upstream In the app, I'm still shown the "Create pull request" suggested next step even though I've already created one. This is very confusing because you already have a PR.Įxample: I'm in billygriffin/desktop (a fork of desktop/desktop) on my branch new-work, and I make some commits and create a pull request targeting the development branch of desktop/desktop.
![github desktop fork update github desktop fork update](https://www.classicpress.net/wp-content/uploads/2020/02/fork.png)
This is conceptually similar to local commits to protected branches, where ideally we wouldn't allow you to do that (because you'd never be able to push those commits to that branch), and instead give you a nice path to somewhere where your work can eventually be pushed without issue.Ī potential solution is outlined in #3918 by Problem 2: "Create pull request" is still a suggestion even after I've created a pull request for the current branch on my fork ( issue here)Īfter you create a PR from a branch of your fork that's targeting the upstream repo, the "Create pull request" suggestion is still displayed. You can't push those changes to the repo you've cloned because you don't have write access, and you can't bring them over to a fork that doesn't yet exist in a low-friction way.ĭesktop could let you know you don't have write access and give you a nice pathway to fork and create a PR. If you've cloned a repo and make some changes with the intent to contribute, you're basically stuck. Update: Solution for this shipped in 2.3! □ □ Problem 1: Trying to push changes to a repo you don't have write access to ( issue here) This process today is confusing and Desktop can make it a lot simpler and help people get out of a bind more easily. These contributions are almost exclusively made via pull requests.
![github desktop fork update github desktop fork update](https://www.earthdatascience.org/images/earth-analytics/git-version-control/git-fork-emphasis.png)
However, we also need to ensure any work we do here doesn't explicitly break for people who are working in "long-running" forks that have entirely diverged from upstream. The primary use case for forks is to contribute to repositories where the person contributing does not have write access. This is a meta issue intended to clarify the landscape around problems related to forks of repositories.