The might look like this: path/to/subfolder - note the lack of leading and trailing path separators. Important: Be sure to use a git bash prompt for the below, and use an editor supporting unix line-ending conventions and save as ANSI when editing the sparse-checkout file, or you may get “error: Sparse checkout leaves no entry on the working directory” errors. This can be edited later to add other folders. git/info hidden folder that will list all the folders you want to include when doing a sparse checkout. This updates the local git config to turn on sparse checkouts, and creates a file in the. You should have a fairly empty looking src folder (it will have the. This is the most likely cause of “error: Sparse checkout leaves no entry on the working directory” errors.įrom a parent of the directory you wish to be the root folder, assuming a folder name of “src” do the following, This grabs the whole repo (which is still required), but does importantly does not perform a checkout, and correctly sets up the origin remote and branch tracking. The file MUST be an ANSI formatted file with UNIX style line endings for git to parse it correctly. This is because otherwise the echo command produces a UNICODE file with a BOM marker. The most important point is this – DO NOT USE POWERSHELL/CMD FOR THESE STEPS – use a git bash prompt. After a bit of research, I found the following steps were minimal and had consistently good results for me – YMMV.
Git sparse checkout windows#
I struggled with setting it up on windows getting a lot of “error: Sparse checkout leaves no entry on the working directory”. It’s worth the effort to set up sparse checkouts on large repositories, everything is much faster! Sparse checkouts enable you to work on a subset of the repository.
From the folder in which you want the source to live, using a git-bash prompt NOT powershell (although see my edit below): git clone –n Įcho some/sub-folder/you/want >.
0 kommentar(er)
