Git Sparse Checkout<\/p>\n\n\n\n
At work we had a very large monorepo. I’m tempted to quote Douglas Adams here but the reference is good enough. Checking out the whole thing runs the possibility of confusing git status messages as a result changes in the other part of the tree. These messages are a distraction. Dealing with them can consume large amounts of time. The best way to avoid them perform what’s called a sparse checkout. This is a checkout that only puts what you need into your working directory. In a normal checkout:<\/p>\n\n\n\n
$ git clone ...\n<\/pre>\n\n\n\nYou get the entire code base in your working directory. A sparse checkout is more complicated to perform:<\/p>\n\n\n\n
$ mkdir _target directory_\n $ cd _target directory_\n $ git init .\n $ git config core.sparsecheckout true\n $ echo \"_your desired subdir_\" >> .git\/info\/sparse-checkout\n $ ## Repeat the echo for each directory you need.\n $ git remote add origin https:\/\/git.neopost.com\/PPT\/IBMHSM.git\n $ git fetch\n $ git checkout master<\/pre>\n\n\n\nIt’s eight steps but if you do it this way, you gain complete control over what’s in your working directory.<\/p>\n","protected":false},"excerpt":{"rendered":"
Git Sparse Checkout At work we had a very large monorepo. I’m tempted to quote Douglas Adams here but the reference is good enough. Checking out the whole thing runs the possibility of confusing git status messages as a result changes in the other part of the tree. These messages are a distraction. Dealing with … <\/p>\n