For more information, see " Troubleshooting cloning errors. 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. It seems to me that there must be some setting, remote string perhaps (or setting since fork is not a git construct), that tells a repo that it is a fork of another.On, navigate to the main page of the repository. If that was not the case, I have been able merge unrelated repositories before using the command line ( merge -allow-unrelated-histories) but this seems a messy way to resolve the 's issue, as it will create duplicate very similar histories. I was happy to delete the above repos and start again, since the changes I wished to make were trivial. Perhaps it was because Desktop behaviour has changes due to software updates since they were created, and these broke Desktop's and 's 'fork detection' behaviour? Change the current working directory to the location where you want the cloned directory. I feel like the above replicated the likely processes I used to create the problem clones. To clone a repository using GitHub CLI, click GitHub CLI, then click. It remains a mystery to me what caused the original incarnations of the above two clones not to be able to be converted to or recognised as forks. I could however go on to create a pull request via, so success in the end. On attempting to sync forks via, it recognises they are not in sync, but presumably as I don't have write privileges to upstream, there is no option for me to sync. Although Desktop did not give me the option to create a pull request, so suspicion! On pushing via Desktop I was asked if I wanted to create a fork. This time I made the changes directly in main and committed them. Just to test whether 'not creating a new branch' was the cause of my pain, I then deleted the other repo's github clone etc., and again created a new clone using GitHub Desktop. Success, I have now been able to make changes, commit locally and create a pull request with original upstream repo as the target. It recognised correctly that I didn't have access to upstream and asked to create a fork at CaverBruce. I then created a new branch and used GitHub Desktop to publish it. However to test the Github Desktop route (to fork creation) and recover from my immediate impasse I deleted one repo's clone and removed it from Github Desktop, TortoiseGit and local drive, and started afresh creating a clone using GitHub Desktop. So I'll take on board that best practice is to fork directly using. Although I have four clone/fork pairs of repos that are working perfectly afaik for some years. What you say makes sense, however for two clone/'fork' pairs of repos I cannot replicate this behaviour.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |