I had this same problem with the SSH keys. The original post is asking about commit attribution and the solution posted seems to address that.

However, I’d like to know if there is a solution to the SSH key problem itself. Is there a way to use SSH with TortoiseGIT and GitHub without having these key conflicts?

Thanks much for any advice anyone has!

Related question when trying to push to Github with TortioseGit. I have copied my public SSH into my Github account. And within TortioseGit I point to my SSH key. However, what is the Github URL supposed to be??? Please provide an example.

This doesn’t work…

ssh://git@github.com:>/Repository.git

The scheme is git@github.com:user/repo.git. You can just click on the green “Code” button on your repository page and select “SSH” in the popup to get the exact URL.

I'm sure this is a no-no to resurrect an old thread, but I'm having essentially the same issue. Commits do not show up as Verified on Github when committing using TortoiseGit. If I commit from the command line it works.

My username and email is set correctly in Github and TortoiseGit.

Viewing the effective config from TortoiseGit everything seems fine. I have a user.signingkey and it is set to ssh.

Like I mentioned from the command line it works just fine.

Just can't figure out what needs set from the TortoiseGit side to get this working.

So I kind of feel bad to Necro this discussion again. But seeing as I didn't actually see a functional resolution listed yet, and I just came across this page, and I did finally get it working. I thought I would share.

So from the original answer, you would need the email and such in Tortoise to match GitHub. From there, the information from @blounsbury-usbr got me going in the right direction. Ultimately this GitHub page detailing setting up the client from the command line was necessary.

@LudiusMaximus original post noted that Puttygen produced a public file that wasn't suitable for GitHub. In Puttygen the UI has the rsa public key right there to copy/paste.

(dummy generated key just for the screenshot - not an actively used key)

In the post if using a Putty key in the UI there, it also would need to be set to use the GitHub SSH address not the https URL for the remote.

For the rest of this I personally ended up just doing it all from the command line because I couldn't find all the relevant settings in the TortoiseGit UI that easily. Afterwards I realized that the file path for the SSH public key can just be pasted into the Signing Key ID field on the Git settings page in the TortoiseGit UI. The other 2 settings listed below I couldn't find UI entries for. So they needed the command line or direct .gitconfig edits anyway.

1. First in GitHub add your public SSH key for signing. If you already have it for connection, you'll need to add it again and select signing. So it will be listed twice.
   
   

2. From a command line run

• git config --global gpg.format ssh
• git config --global user.signingkey /PATH/TO/.SSH/KEY.PUB
  This last one is what tells it to actually sign things.
• git config --global commit.gpgsign true

If you'd rather edit the Global .gitconfig directly you could do that too. The relevant changes to make would be

Under [user] add

	signingkey = /PATH/TO/.SSH/KEY.PUB

If you're on Windows replace any / with 2 \\ ie C:\\PATH\\TO\\.SSH\\KEY.PUB

Then add the following if they don't already exist

[gpg]
	format = ssh
[commit]
	gpgsign = true

so it would look something like this

And before I get spammed about how insecure it is to keep the key there, this is only to illustrate how it would look. That's not where I keep my keys.

If all was done correctly then after the next local commit and then push to GitHub you should have a nice green Verified on the commit.