What Happens When You Git Checkout After Cloning Clone a Git repository, and by default you actually check out the branch that HEAD points to in the original repo. Still, if you wish to check out a branch or tag right after cloning there is optional command like -b during the clone operation; You can use this to directly point the new HEAD to a branch other than default one.
Cloning with a Particular Branch
To clone a repository and get to a specific branch, you need the following command :
bashgit clone -b .-nONSEBOSSED-GIT_REPOSITORY_URL
This command clones the repository and checks out to specified branch simultaneously. As usual, if the branch doest not exists then Git wont recognize it and will return an error.
2. Detached HEAD State Explained
After cloning, and in case you want to switch between the different commits or tags (and checks out them), it can be done as a follow:
bashgit checkout
This will detach HEAD at that commit, which is to say you wont be on a branch so your commits won’t belongto any brancheci;i??ed point of time in your project. This is helpful for looking at old states of your project without changing anything in any branch you have right now.
3.Git (ad) Efficiency with Sparse Checkout
When cases in which you only care about particular directories or files from a large repo, use sparse-checkout with partial cloning:
The above command will clone the empty repository so you can start by cloning any remote git repo using the –filter with blob:none –>
sparse.
Only after cloning, you have the ability to do a sparse checkout and include only paths that are needed which can help in downloading lesser amount data thereby making it much more performance processData volume applied recursively for each Kloena repository，默认行为进行了递归应用到每个单一的仓库工程 If…streams read from central ifne connection with automatic ACKStreaming media or otherwise uncollectible.
You can manage those workflows more effectively using these commands and options with you when working in Git after cloning a repository.