#Update fork github desktop full

You can still create a branch off it, it's just not automatic. However, at least using the command-line git tools, checking out a remote branch (whether it's 'origin/3.x' or 'upstream/3.x') is a temporary operation – it doesn't automatically create a local branch that you can work on, it only checks out a 'detached' commit. to track someone else's development fork.) (This is more general than just 'upstream', you can configure any number of remotes, e.g.

#Update fork github desktop full

Your desktop repo has full copies of all branches from the upstream repo (as of the last fetch) and you can check out their commits, create local branches off them, merge or cherry-pick individual commits into a local branch, etc. If the upstream repo has some commits ahead of my fork on the 3.x branch and I click on upstream/3.x, does my working directory somehow gain the changes from those upstream commits? For example, you might integrate the newest upstream changes by merging 'upstream/3.x' into your local '3.x', then push to your GitHub fork's 'origin/3.x'. Git repositories aren't limited to having a single URL to push/pull from – it is very common to have two when working with forks, and to directly fetch commits and branches from both. (Neither the 'origin/' branches nor 'upstream/' ones are actually local to the repo that GH Desktop is showing they're only locally cached copies of remote branches.) The cloned repository that you have on your desktop is fully separate from the fork that you have on GitHub – it has its own branches and everything. You're not only working on a fork you're working on a fork of the fork. How is it possible that I could switch to a branch on the upstream repo if I'm working on a fork? Diverging is expected, so the branches downloaded from a remote repository are always namespaced with 'reponame/', while Hg's docs imply that a diverged bookmark is supposed to be dealt with quickly.) Though it seems that Git branches aren't kept as strictly in sync with the remote repository as Hg bookmarks are. And similarly, when you create a new local branch off 'master', it's just creating a second bookmark that points to the same commit as 'master'. branch) is updated to point to them, so now both the local and remote bookmarks independently point to the same commit. (In fact, that's what happens when you push to GitHub – first the commits are uploaded, and then the remote repository's 'main' or 'master' bookmark (i.e. They're not immutably attached to commits but act as flexible pointers to some commit ID (see Mercurial's Bookmarks docs), so it is entirely possible for several repositories to have their own bookmarks pointing to the same commit. Git branches work like Mercurial's bookmarks. For more information, see ' Troubleshooting cloning errors.(but bear in mind I come from a Mercurial background so maybe I'm not fully understanding Git's branches - I think they exist outside the version control somehow?).

The default branch you want to clone still exists.

For more information, see ' Troubleshooting cloning errors.'

You have permission to access the repository you want to clone.

If you're unable to clone a repository, check that:

When cloning a repository it's possible that you might encounter some errors. > remove: Total 10 (delta 1), reused 10 (delta 1) > Unpacking objects: 100% (10/10), done. > remote: Compressing objects: 100% (8/8), done. $ git clone > Cloning into `Spoon-Knife`. Type git clone, and then paste the URL you copied earlier. Īlternatively, to clone your repository in Desktop, click Set up in Desktop and follow the prompts to complete the clone.Ĭhange the current working directory to the location where you want the cloned directory. To clone the repository using an SSH key, including a certificate issued by your organization's SSH certificate authority, click SSH, then click.

To clone your repository using the command line using HTTPS, under 'Quick setup', click. It's often made if you don't initialize the repository with a README when creating it. To clone and open the repository with GitHub Desktop, click Open with GitHub Desktop.įollow the prompts in GitHub Desktop to complete the clone.įor more information, see ' Cloning a repository from GitHub to GitHub Desktop.' Cloning an empty repositoryĪn empty repository contains no files.

On, navigate to the main page of the repository.