Re: Creating sparse checkout in a new linked git worktree

From: Duy Nguyen <pclouds@gmail.com>
Date: Jan 28, 2018, 09:40 UTC
Message-ID: <CACsJy8D03LkoT38Xrz0xDUk=Uf=9O0XKrLG0vZMtBxowo9ibNA@mail.gmail.com>
In-Reply-To: <CAPig+cSP0UiEBXSCi7Ua099eOdpMk8R=JtAjPuUavRF4z0R0Vg@mail.gmail.com>

On Sun, Jan 28, 2018 at 2:25 PM, Eric Sunshine <sunshine@sunshineco.com> wrote:

Show 19 quoted lines

> On Wed, Jan 24, 2018 at 11:11 AM, Jessie Hernandez
> <git@jessiehernandez.com> wrote:
>> I am trying to get a sparse checkout in a linked worktree but cannot get
>> it working. I have tried the following
>>
>> * git worktree add /some/new/path/new-branch --no-checkout
>> * git config core.sparseCheckout true
>> * <add the directory I would like to checkout out to
>> $GIT_DIR/info/sparse-checkout>
>> * cd  /some/new/path/new-branch
>> * git read-tree -mu sparse-checkout
>>
>> But I still end up with a fully populated worktree.
>> Is there something I am missing or doing wrong?
>
> The sparse-checkout file is specific to each worktree, which allows
> you to control "sparsity" on a worktree by worktree basis. Therefore,
> you should create $GIT_DIR/worktrees/<id>/info/sparse-checkout instead
> (where <id> is "new-branch" in your example).

Nit. Do

    $EDITOR `git rev-parse --git-path info/sparse-checkout`

if you're already in the right worktree so you don't have to find out about <id> or the full path.

I wanted to add "git checkout --edit-sparse" for some time. Using it in multiple worktrees may be a good push for me to eventually do it.

-- 
Duy