There's not much to it really. It's just an ed25519 key which has the same 64 byte hex string that nostr does for its privkey. So nostr already has an an ed25519 privkey which is native to git. It can do commits, ssh, clones, git identity etc. The #pubky is simply a base32 encoded public key in the profile (just like npub but better, without the unnecessary segwit checksum). So every nostr account gets both functionalities. Perfect for git.
Discussion
I think what your saying is that it can already do some of what an ssh key can do with git because of its inherent properties.
I find it really difficult to understand the thinking here. Nostr privkeys are both nostr keys and git keys. But the argument I want to use them only as nostr keys, rather than use them both nostr keys and git keys, I cannot see as a technical argument. I just cant see it. It's like having the number "2" and saying, we can use that to add, but not to multiply. It's a thought process that I find alien, and see no way past it.
I'm not suggesting that support shouldnt be added to git for signing commits with nostr keys. It just seems there is a lower value proposition on focusing on that right now compared to the other #GitViaNostr tasks
