![github desktop forked github desktop forked](https://www.classicpress.net/wp-content/uploads/2020/02/step1-fork4.png)
![github desktop forked github desktop forked](https://static.filehorse.com/screenshots/developer-tools/github-desktop-screenshot-01.png)
With the current method this isnt a method which i can do so as i cannot see local PR's. do a pull request to the head, so that the head would be insync with commits from the upstream.push the newly merged branch to github.use github desktop to merge the local pull request branch into the local duplicate master branch.use github desktop to create a "local" branch which is a duplicate of the master branch.For information about forking on, see the web browser version of this article. use github desktop to create a "local" branch with the pull request files. You can fork a repository on or in GitHub Desktop.make a pull request from the heads head repo to my repo.I'm due to do another upstream later this evening should you want to shadow and see how i would primarily use github desktop. Do you remember what option you selected when cloning this repository You can change this by going to Repository > Repository Settings > Fork Behavior. The previous setup was better as you could see your PR's, meaning if i wanted to upstream from the head's head i could pull their changes and PR it to my fork's head repo ensuring they are in sync.ĭue to the new changes, i'm unable to maintain my fork by making a pull request from upstream. When you clone a fork in GitHub Desktop it gives you the option of choosing how you want to use the fork: This option affects what default branch new branches are based off of. The head repository is an open source project which is a fork of another open source project, meaning multiple people will contribute to both projects, however, it is only a select few people have access to create branches.ĭue to this, should you wish to contribute, you will need to maintain your fork, keep it up to date etc.