Jelmer Vernooij

Pushing tags to existing repositories (and Dulwich forks) is fine; the only thing that doesn't work is pushing the existing Dulwich history to an empty repository. This isn't an actual...

Is publishing a fork / shallow clone not an option?

I've been hesitant to go the route of rewriting history, because it breaks all forks and PRs. However, if having these commits is too painful we can consider it.

If you wanted to work on it, I think here is a possible way to approach this: 1) Provide a script to rewrite history, and add a headsup in README...

I'm open to merging PRs that add pathlib support, but I don't believe there's anywhere in Dulwich today that promises pathlib support.

Ah, I see. That's meant for plain str since RefsContainer uses bytes internally.

There are conventions, but not particularly well documented. We should improve that and add more type signatures. It's basically: * Porcelain tries to work with strings (and generally accepts either...

Yep.

I'm open to PRs that add more use of os.fspath to dulwich.porcelain in particular, if somebody wanted to work on that.

This format doesn't appear to be used by default as far as I can tell (on git 2.37 here). Perhaps in specific circumstances only? I don't have concrete plans to...