feat: upgrade go-git to v5.5.1 - #963

There is also #947, but it looks like some things are breaking in git-bug.

Yeah ... I didn't notice the one started by dependabot. I'm tracking down the Go panic (it's the crypto checking the signing).

We should talk about what our goals are for commit signing and use cases for those who already have keys. This will obviously also impact how the bridges work since ideally we'd be able to verify signed commits from the "forges".

We should talk about what our goals are for commit signing and use cases for those who already have keys. This will obviously also impact how the bridges work since ideally we'd be able to verify signed commits from the "forges".

Does that answer your question? #130

As for the bridges, I'd think the only interaction with keys would be to import the public keys when creating or updating the identities. That way, anyone having the matching private key would be able to adopt the identity without losing the history.

I'll add a few comments to #130 instead of them languishing here on a closed PR.