With git1.8.4 (July 2013), in addition git shallow update for submodule (git submodule update –depth 1), you now can have a custom update: In addition to the choice from “rebase, merge, or checkout-detach”, “submodule update” can allow a custom command to be used in to update the working tree of submodules via the “submodule.*.update” configuration … Read more
–depth is a git fetch option. I see the doc doesn’t really highlight that git clone does a fetch. When you fetch, the two repos swap info on who has what by starting from the remote’s heads and searching backward for the most recent shared commit in the fetched refs’ histories, then filling in all … Read more
You can do a git clone <git_url> delete the .git repository from your folder. Which will delete all your history. The you can do a git init which will create an entirely new git project for you. This may not be the best way. But this will work . Hope it helps.
To clone repo foo.git with branch bar do: git clone –depth 1 https://path/to/repo/foo.git -b bar See the git-clone documentation: https://www.kernel.org/pub/software/scm/git/docs/git-clone.html
Starting with Git 2.5.0 (which needs to be available at both the client and server side) you can set uploadpack.allowReachableSHA1InWant=true on the server side to enable fetching of specific SHA1s: git init git remote add origin <url> git fetch –depth 1 origin <sha1> git checkout FETCH_HEAD Note that I did not find a syntax to … Read more
After doing a shallow clone, to be able to checkout other branches from remote, Run (thanks @jthill) doc about set-branches: git remote set-branches origin ‘*’ After that, do a git fetch -v –depth=1 Finally git checkout the-branch-i-ve-been-looking-for Step 1 can also be done manually by editing .git/config. For instance, change the folloing line from: fetch … Read more