Setting up GitHub Desktop for Raspberry Pi?

I am looking for a way to set up Github Desktop to push code to a local repository on my Raspberry Pi.

Anyone here have done this before? Is it even possible?

I have already managed to get it to work with the command line stuff over SSH, but the problem is that it asks me for a password every time which is extemely annoying and I can’t effectively see diffs.

I cannot seem to work around the password problem, no matter what settings I use for credential helper, it always asks me for a password. And I cannot find any good information on how to set up SSH keys for this.

The repo almost works in GitHub Dekstop but it never tries to ask me for a password or anything, it just tries with whatever password it tries with and displays an error message.

Any help? This is seemigly something that is supposed to be very easy but nothing works.

1 Like

I assume that you’re on macOS? If this is true, you may want to add the following at the bottom of your ~/.ssh/config file:

Host *
    UseKeychain yes

This instructs the ssh system on macOS to use Keychain to cache the password. That may also fix Desktop as well.

I hope that helps!

Nope, I am on Windows using GitSCM (, the same thing that GitHub Dekstop uses.

Ok I figured it out after some more googling about.

What you have to do is generate an SSH key on the Windows machine using Git Bash’s  ssh-keygen , and then copy the public key C:/Users/<user>/.ssh/ to the Raspberry PI’s /home/<user>/.ssh/authorized_keys

Next you want to establish the first connection manually through Git Bash, so just cd into your cloned repo and do something like git pull, it will complain that the authenticity of the host cannot be established and if you want to connect anyway, you say yes and it will generate ~/.ssh/known_hosts on the Windows machine and now you can use GitHub Dekstop to push code to your Raspberry PI repo.

A bit sad that this isn’t handled in the GUI of GitHub Desktop, but at least it works.

Hey @robotboy655 , 

Thanks for here and taking the time to come back and share your fix, we’ll pass on the feedback to our team. Thanks again!