Sebastian Thiel

Could it be that there is some sort of name-duplication with virtual branches? That way, you might have deleted virtual branches which somehow shadowed the real ones. I was also...

Thanks for sharing! I know that GItButler now creates real branches for everything it finds `.git/gitbutler/virtual_branches.toml`, so if the zombie-branch is mentioned there, there is reason to believe that GitButler...

@orhun This analysis is quite old and might not be accurate anymore. But if it is, then moving it to `gitoxide` should give a performance boost, along with easier parallelization...

Thanks for sharing your experiences! Unfortunately it's expected to be somewhat rough at the moment. Searching by term in the `gix` docs on `docs.rs` is the way to go though,...

Thanks for letting me know, also where to get one of these repositories and that Git can already clone it! It's some time out until SHA256 will be supported, but...

> This sounds like it could be very easily worked around. In my case, I'm using [Starship](https://github.com/starship/starship), which strongly depends on this tool and due to this issue, the repository...

Thanks a lot for setting up this issue! > @Byron _You have suggested some good ideas, which I have not covered here, because I don't know if you prefer to...

The debug version always prints with surrounding `""`, and they are used to indicate that the debug version is actually needed to be 'display-safe'.

> I would expect to debug-print to a buffer and then printing that buffer to be slower than checking whether the string is display-safe and then either normal or display-safe...

Thanks for chiming in. I also think that would be fastest, but would also require the parts that are 'vulnerable' to be retrofitted. There probably isn't too many of these,...