I have recently been active on github since I kicked off with my project, around the beginning of 3rd year. I understood most technicalities (though it does require a considerable amount of grit and sometimes hours of hacking through commands to get the right one), but adding an SSH was taking its toll on me until this moment.
Yes, I have succeeded in pairing my machine with github using a SSH connection instead of an HTTPS connection.
This is much easier in many ways:-
What adding an SSH key does is that, it establishes the identity of a computer as a trusted machine, and doesn’t need to authenticate it again and again through a password whenever the machine wishes to contribute something to the website.
Also, Since I had kept a pretty long username and password, entering it every time I wanted to push something to my github account was becoming a big hassle for me.
So what exactly does SSH stand for?
Secure Shell (SSH), sometimes known as Secure Socket Shell, is a UNIX-based command interface and protocol for securely getting access to a remote computer. It is widely used by network administrators to control Web and other kinds of servers remotely. It provides authentication and a secure connection when trying to move files from one machine to a server, or another machine.
Some links that can tell you more about SSH:-
Contributing to github feels so much more easier after adding an SSH key. I used thje following documentation to do it. It’s really simple, you just have to follow it word by word. Even if you get stuck, just put up a query on any of the linux forums. The good part about linux is that there is a lot of developer support for all Ooperating Systems based on linux kernel.
You can also change a connection type of a pre-existing HTTPS clone of a repository into a SSH clone and vice-versa.
Try reaading some more links if you’re more interested in this:-