The moment I switched to repo1 Git started noticing the changed files. Sometimes you cant do a fetch if the branch you were working on is deleted, and you have some changes that you dont want to commit. Then colleague of mine observed it as independent pair of eyes and brought this thing to my notice that I was in wrong but very similar looking repository. Nothing to commit, working directory cleanįor half an hour. So, I just kept running command git status on repo1 and it kept giving the same message So without realizing I modified an exactly same named file in repo2 which I was supposed to change in repo1. Now the thing is that as a standard guideline, the directory structure of source code of all the products is exactly the same in my company. See that master is not listed as the default. Click Current Branch to list the branches. Open GitHub Desktop and switch to the local copy of the repo. To the right of the title of the pull request, click Code, then, on the Local tab, click Checkout with GitHub Desktop. In the list of pull requests, click the pull request that you would like to open in GitHub Desktop. Under your repository name, click Pull requests. Go to the remote repo and verify that master is set as the default. Opening a pull request in GitHub Desktop from GitHub. These two repositories are essentially the repositories of two products I work off and on in my company. GitHub Desktop 2.6.1 MacOS Big Sur, Version 11.1. My story is bit funny but I thought it can happen with someone who might be having a similar scenario so sharing it here.Īctually on my machine, I had two separate git repositories repo1 and repo2 configured in the same root directory named source. TL DR Are you even on the correct repository?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |