SSL_connect: SSL_ERROR_SYSCALL in connection to :443.destination path already exists and is not an empty directory.Git is not working after macOS Update (xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools).Git fatal: protocol 'https' is not supported.Does the target directory for a git clone have to match the repo name?.The next steps to follow if no configuration exists for git pull, have already been explained by other answers. If that is the case, then the part where it shows "Local branch configured for 'git pull':", would be missing from the output of git remote show origin. But if you have added a remote manually using git remote add, these are missing from the git config. Initially, if you have cloned the repository, using git clone, these things are automatically taken care of. In this case, git pull will refer to git pull origin master Please note the part where it shows, Local branch configured for git pull. If you run the command, git remote show origin, (assuming origin as the short name for remote), git shows this info, whether any default reference exists for git pull or not.īelow is a sample output.(taken from git documentation). Just wanted to add some info that, we can check this info whether git pull automatically refers to any branch or not. Git will then push to that corresponding branch automatically: (gh-pages)$ git push When you have tosetupmerge set to true and checkout a branch for the first time, Git will tell you about tracking the corresponding remote branch: (master)$ git checkout gh-pagesīranch gh-pages set up to track remote branch gh-pages from origin. Kind of magic, IMHO but this might help in cases where the specific branch is always the current branch. It's called a tracking branch which git ready recommends setting by default.įor the next repository above the present working directory: git config tosetupmerge trueįor all Git repositories, that are not configured otherwise: git config -global tosetupmerge true There is also a way of configuring Git so, it always pulls and pushes the equivalent remote branch to the branch currently checked out to the working copy. I can tell git pull which branch to merge, and it works correctly, but git pull does not work as it did originally before my git checkout. If you often merge with the same branch, you may want toĬonfigure the following variables in your configuration See git-pull(1) for details on the refspec. Name which branch you want to merge on the command line and Your configuration file does not tell me either. You asked me to pull without telling me which branch you Currently, git pull results in: -bash-3.1$ git pull UPDATE 2: To be clear, I understand that my original method may have been incorrect, but I need to fix this repo so that I can simply use git pull again. What has changed which does not allow me to do a straight git pull without specifying origin master, and how to I change it back?įetch = refs/heads/*:refs/remotes/origin/* Now, I can not pull using a straight git pull but instead, have to specify git pull origin master, which is annoying, and indicates to me that I don't fully understand what is going on. When I was again ready to pull, I found that I had to set my branch back to master. Recently, I had to revert to a previous branch, and did so with git checkout 4f82a29. In each project, I always git clone and from that point, can always git pull, so long as I don't have outstanding changes, of course. I'm not a git master, but I have been working with it for some time now, with several different projects.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |