Sebastian Thiel

Thanks for sharing, @OPeyrusse, technically there will soon be nothing in the way of allowing worktrees, once we validated that it indeed is working as it should in those checkouts.

I have linked #10677 as rough ideation on what could be possible in future. And that future will come, once we have covered: * apply/unapply * updating workspaces, stacks, pushing...

Thanks a lot for reporting! To fix this, GitPython should control for this flag and turn it off when invoking Git, i.e. with `git -c mnemonicPrefix=false`.

Thanks a lot for reporting! I took a look and believe it should be possible to teach it to deal with such repositories as it's only using plumbing. https://github.com/GitoxideLabs/gitoxide/blob/6281e1ac140c939b046ac88d536f16e076a3206c/gitoxide-core/src/organize.rs#L23-L39 It...

I thought I could quickly try it out and make it work, but realized my Git as of version 2.39.5 (from 2024-05-30) doesn't yet support `--ref-format` anywhere. On CI that's...

That's interesting! ``` ❯ git --version git version 2.39.5 (Apple Git-154) ``` It seems then that either I checked out the wrong tag or the version given here is something...

I found the date confusing, it said: `(29-Apr-2024)`, while 2.39.5 is from `2024-05-30`. Hence I thought 2.39.5 should have it already. `cargo test -p [email protected]` should do the trick.

A `.tar` file should have been written. If the test along with it is submitted as a PR I can take it from there.

Sorry for the confusion - I missed that `make_basic_repo.sh` has been excluded from the tar-file generation. Thus the change was only made locally, and what's worse is that I won't...

Actually there is a way. The script the test was in originally is not producing a tar file, but any other file will. Hence, the test could move into `make_reftable_repo.sh`...