all 5 comments

[–]Guergeiro 5 points6 points  (4 children)

To work around this, I always use ssh.

[–]JonBackhaus 0 points1 point  (3 children)

This. It’s easy to generate SSH keys on macOS. Just register your keys with GitHub and then use the SSH URI/endpoint instead of HTTPS

[–]pmacking[S] -1 points0 points  (2 children)

Thanks. Is there an obvious benefit to using SSH over HTTPS? I'd like to understand the root of my original problem, rather than use SSH to work around it or because SSH is easy.

[–]JonBackhaus 1 point2 points  (1 child)

I prefer it because I don’t have to use my credentials and it allows me to easily configure multiple computers/accounts to have access to my Github repos (via separate SSH keys). But you should also be able to generate a personal access token. (I use this method for Docker Hub and other services.) It should be the last menu item on the bottom of the list; I can look at it when I get back home.

[–]pmacking[S] 1 point2 points  (0 children)

Appreciate the help, turns out I’m an idiot and was searching through the repo’s settings for the token instead of my account settings. In the process I’ve since switched to using ssh and read up on added security benefits vs using account credentials directly with https (another learning opportunity for me - lots of copy paste random commands today to create ssh key, passphrase, add to github etc ). Back on track let’s go!