In addition to the response above that describes how to set the remote repository for an existing branch in your local copy, I felt it would be worthwhile to expand on this, by noting that while a default remote cannot be setup for git pull, a default remote can be set for git checkout in … Read more
what worked for me is , remove .git folder copy .git from other repo now git checkout Before Removing , You can try git fetch –all git reset –hard origin/master You will need to replace master with the appropriate branch, which now defaults to main.
There are three simple solutions to copy the last version that is in you remote repository, discarding all changes that you have made locally: Discard your repository and clone again. This is the most simple solution, but if your repository is big, it can take a long time, and may require extra effort like reconfigureing, … Read more
I had this question, too. I found the answer in the git documentation (https://git-scm.com/docs/git). Run the command git -C <git-working-directory> pull <git remote> The specific command to answer this question is git -C checkout/myApp/ pull Note that it is important -C <git-working-directory> comes before the pull command and any additional pull options can be specified … Read more
I was looking for the same thing and finally found the answer that worked for me in another stackoverflow post: Merge, update, and pull Git branches without using checkouts Basically: git fetch <remote> <srcBranch>:<destBranch> Example: git fetch origin branchname:branchname
Quick “TL;DR” take-away version, so one can come back later and study more git stash hangs a stash-bag—this is a peculiar form of a merge commit that is not on any branch—on the current HEAD commit. A later git stash apply, when you’re at any commit—probably a different commit—then tries to restore the changes git … Read more
“git merge –squash” (after “git fetch”; “git pull” is just fetch+merge, pehaps it also allows –squash option) might be what you want. From git-merge(1): –squash Produce the working tree and index state as if a real merge happened, but do not actually make a commit or move the HEAD, nor record $GIT_DIR/MERGE_HEAD to cause the … Read more
git fetch origin git reset –hard origin/master git pull Explanation: Fetch will download everything from another repository, in this case, the one marked as “origin”. Reset will discard changes and revert to the mentioned branch, “master” in repository “origin”. Pull will just get everything from a remote repository and integrate. See documentation at http://git-scm.com/docs.
git fetch git reset –hard origin/master
As Julian said see https://confluence.atlassian.com/display/FISHKB/Git+indexing+fails+due+to+bad+pack+header It really can be a memory issue, and to make sure we don’t lose the solution here it is: git config –global pack.windowMemory “100m” git config –global pack.SizeLimit “100m” git config –global pack.threads “1”