Git

To know which files are going to be modified, you have to start by fetching the branches fetch git then to see the files git log -p HEAD.. origin and the differences (three dots, not two) git diff HEAD… origin

To recover deleted files automatically without specifying the path git ls-files -d xargs git checkout —

Since git 1.7.0 it is possible to use a technique called sparse checkout The steps for cloning are: Mkdir<repo></repo> Cd<repo></repo> git init git remote add -f origin<url></url> This creates an empty folder, runs the fetches but without checking out the files. Then you have to configure git to use sparseCheckout. git config core.sparseCheckout true Then … Read more

Sometimes when you work with git, you don’t find all the remote branches. Even after using git fetch they do not appear. fetch git it is very likely that the origin of the fetch is wrong. We can see, for example, that here only the master branch is updated. $ git config –get remote.origin.fetch ‘refs/heads/master:refs/remotes/origin/master … Read more

After a sprint, all the local branches you have are useless and take up space. Below is a small command to remove them (except master) git branch grep -v “master” xargs git branch -D

To list local and remote branches $ git branch -a remotes only $ git branch -r For the list to be up to date you can use $ git remote update $ git remote plum origin