git bisect stuck - --force flag required for checkout

Devste Devste· Dec 21, 2023, 10:47 UTC · lore

Thank you for filling out a Git bug report! Please answer the following questions to help us understand your issue.

What did you do before the bug happened? (Steps to reproduce your issue) add file Foo.txt to .git and commit add some commits with any changes to other files, as this is needed for reproduction run: git config core.ignorecase false rename Foo.txt to foo.txt and commit add some commits with any changes to other files, as this is needed for reproduction run: git bisect start && git bisect bad eventually, when running "git bisect good" (or bad) you will get an error:

>error: The following untracked working tree files would be overwritten by checkout:
>Foo.php

Anything else you want to add: git bisect good/bad needs to have support for a "--force" flag, which is passed to the git checkout it runs internally At the moment git bisect cannot be used on Windows, as there is no way to continue the bisect from here. Changing the "git config core.ignorecase true" temporarily is not an option, as this will introduce a variety of other bugs, which, on Windows, eventually will require you to completely delete and reclone the repo, as Windows file paths are case-insensitive

[System Info] git version: git version 2.39.1.windows.1 cpu: i686 built from commit: b03dafd9c26b06c92d509a07ab01b01e6d0d85ee sizeof-long: 4 sizeof-size_t: 4 shell-path: /bin/sh feature: fsmonitor--daemon uname: Windows 10.0 compiler info: gnuc: 12.2 libc info: no libc information available

[Enabled Hooks]

brian m. carlson· Dec 21, 2023, 12:22 UTC · re: Devste Devste · lore

Re: git bisect stuck - --force flag required for checkout

On 2023-12-21 at 10:47:57, Devste Devste wrote:

Show 8 quoted lines

> Thank you for filling out a Git bug report!
> Please answer the following questions to help us understand your issue.
> 
> What did you do before the bug happened? (Steps to reproduce your issue)
> add file Foo.txt to .git and commit
> add some commits with any changes to other files, as this is needed
> for reproduction
> run: git config core.ignorecase false

`core.ignorecase` is specifically designed for this case. It's set internally by Git when the repository is created, and it's not supposed to be changed by the user.

If you want a repository where there's no case sensitivity, then I'd recommend WSL. It's also possible to make some directories case sensitive in Windows 10 and newer and allegedly that works recursively, so you could use `fsutil` to do that, then run `git init`, then add data.

Show 17 quoted lines

> rename Foo.txt to foo.txt and commit
> add some commits with any changes to other files, as this is needed
> for reproduction
> run: git bisect start && git bisect bad
> eventually, when running "git bisect good" (or bad) you will get an error:
> >error: The following untracked working tree files would be overwritten by checkout:
> >Foo.php
> 
> Anything else you want to add:
> git bisect good/bad needs to have support for a "--force" flag, which
> is passed to the git checkout it runs internally
> At the moment git bisect cannot be used on Windows, as there is no way
> to continue the bisect from here.
> Changing the "git config core.ignorecase true" temporarily is not an
> option, as this will introduce a variety of other bugs,
> which, on Windows, eventually will require you to completely delete
> and reclone the repo, as Windows file paths are case-insensitive

Could you share what those problems are? `core.ignorecase` is specifically designed to deal with case-insensitive file systems, and that's why Git sets it to true.

-- 
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA