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? I feel like the above replicated the likely processes I used to create the problem clones. 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. is the number 1 seller for programming prints with 100% exclusively designed canvases.Thanks steveward. Make your room come alive with the coolest programming/coding canvases on the market. Thank you, if you like my rambling check out my personal blogging site at That's all there is to it, it's very simple and the GitHub desktop tool helps speed up the process - it also helps in actually understanding what these bloody commands are doing! Go to your forked repo on Github and make sure your changes have been added:Ĭheck over the changes then click Create Pull Request!įinally, wait for your beautiful code to be merged! Push the changes to your forked repository: Step 3 - Clone the forked repository using GitHub desktop In this example, I am going to make a pull request to a friend's repository and just update their readme.md Go to the repository - at the top right of the page, there should be a fork button! Step 2 - Fork the repository you want to make the pull request to! Once downloaded and installed I'd recommend having a little watch of this video to get up to speed with it - it's definitely worth a watch: I just recently moved to GitHub desktop it is so much faster and just an all-round more pleasant experience. I myself have spent many years using the CLI making many, many mistakes. Cry when you see the long string of commands that need to be entered and memorised.Google: "How to make make a pull request".
I'm sure many of you have done the following: