Repository navigation
Git index version 3 support #1960
Description
Using git python to add files to an index fails at an index head assertion if the local repo is being otherwise worked on with git 2.46.0:
Lines 209 to 210 in cfadd9e
Is it planned to add support for version 3 soon?
I couldn't find any ticket tracking this, so apologies if this is a duplicate.
Activity
Byron commentedon Sep 6, 2024
There is no plan to add support for extended index flag in V3, even though it would probably be quite easy to add if someone wanted to contribute support for it.
Generally, I probably wouldn't trust the index implementation as it is here and if possible,
repo.gitmight be able to do the same with a decent amount of convenience.mgorny commentedon Nov 4, 2024
For the record, the workaround is to set:
and clone the repo again (or use
-c feature.manyFiles=falsewhen cloning it).tombedor commentedon Jun 17, 2025
Made a PR to make errors from using an unsupported version a bit easier to debug: #2055
Byron commentedon Jun 18, 2025
It's a bit sad that the custom index implementation is half-baked only, and a little wonder that people can use it at all. In retrospect, it would have been better to only use Git for index manipulation. Maybe it's possible to workaround with
repo.gitas well.misrasaurabh1 commentedon Nov 15, 2025
thank you, index v3 support will help fix a crash for us.
Byron commentedon Jul 20, 2026
--- agent
This has been implemented by merged PR #2081, “Preliminary support for index format v3,” merged on November 9, 2025. Current GitPython code accepts index versions 1–3 and writes version 3 when extended flags are present. Closing this issue as resolved.
test: verify GitPython index-v3 support already works (closes Aider-A…