git sparse-checkout (with --filter=blob:none and/or worktreeconfig) does not work with TortoiseGit

What steps will reproduce the problem?

1. git clone --filter=blob:none --sparse <url>
2. cd repo-name
3. git sparse-checkout init --cone
4. git sparse-checkout set dir-name
5. Change some file and use TortoiseGit - Git Commit -> "master"

The following error message appears:

What is the expected output? What do you see instead?

• Changes should be commited to local branch
• Push to server should be possible

What version of TortoiseGit and Git are you using? On what operating system?

• Windows 10
• TortoiseGit 2.11.0.0
• Git 2.28.0.windows.1

changed the description

added enhancement label

I have exact the same problem.
I have a sparse checkout of an embebbed linux application on windows 10.
Reason to use sparse checkout is that i cannot checkout the kernel files on windows.
There are some files like PRN, AUX that windows does not like and some files with case-sensitive names that windows does not like too.
I am using git from bash and use "Git Extensions".
But i like the shell extensions on Tortoise so much that i really miss it in this project.

mentioned in issue #3697 (closed)

The problem is not the sparse-checkout alone. Sparse-checkouts work fine.

Only when combining sparse-checkout --sparse with --filter=blob:none (i.e. the newish partial clone feature: Link1, Link2), do I get that problem.
Maby the heading of this issue should be changed accordingly.

See here for the commands to test --sparse with --filter=blob:none.

I haven't tested on my own, do icon overlays work with sparse-checkouts?

Yes. Works fine, as long as you do not use partial clone flags --filter=blob:none

By the way... it seems that libgit2 does not yet support partial clones (--filter), or maby there is some work-in-progress (?): https://github.com/libgit2/libgit2/issues/5564

In a short test (based on a full normal clone): As soon as I issue git sparse-checkout init (with Git 2.30) libgit2 fails (cf. https://github.com/libgit2/libgit2/issues/5442).

changed title from git sparse-checkout does not work with TortoiseGit to git sparse-checkout (with --filter=blob:none and/or worktreeconfig) does not work with TortoiseGit

changed the description

It is very interesting.

This works fine for tortoisegit:

git clone --sparse https://gitlab.com/tortoisegit/tortoisegit.git myexperiment
cd  myexperiment
git sparse-checkout set 'src/*' # echo 'src/*' > .git/info/sparse-checkout
git checkout

# check .git/config
git config --local --list | grep core.repositoryformatversion 
                         # shows core.repositoryformatversion=0

explorer . # open explorer and try right-click TortoiseGit->Show Log
           # Everything works

Now go back to Git Bash and make these changes, to see it fail:

git sparse-checkout init

# check .git/config
git config --local --list | grep core.repositoryformatversion 
                 # Aha!!!! shows core.repositoryformatversion=1

explorer . # open explorer and try right-click TortoiseGit->Show Log
           # FAIL !!!!

Now go back to Git Bash and "repair" it:

git config --local core.repositoryformatversion 0

# check .git/config
git config --local --list | grep core.repositoryformatversion 
                        # shows core.repositoryformatversion=0

explorer . # open explorer and try right-click TortoiseGit->Show Log
           # works again!!!!

I tried something similar with --filter=blob:none and it seems to be similar, if I recall correctly.

So the thing to research would be core.repositoryformatversion.

Note also: I'm not sure if it is safe to actually do
git config --local core.repositoryformatversion 0

The easy way to fix (w/o messing with repositoryformatversion) would be to delete extension.worktreeconfig from .git/config and integrate the contents of .git/config.worktree into .git/config.

Thank You, Sven - THIS works !!!

mentioned in issue #3822 (closed)

mentioned in issue #3824 (closed)

mentioned in issue #3966 (closed)

mentioned in merge request !232 (merged)

closed with merge request !232 (merged)

reopened

mentioned in issue #4189 (closed)