+[2020-05-10T11:12:15Z]jhasseven manually that one copy paste doesn't seem like that much extra work +[2020-05-10T17:03:04Z]SuperLagjhass: I'm back. Same issue as before. :/ +[2020-05-10T17:03:56Z]SuperLagjhass: I'm running Windows 10, w/WSL instances. However, in this case... I copied working keys to a VM on a VMware host. +[2020-05-10T17:05:08Z]SuperLagkey permissions & ownership are exactly the same as the WSL instance where things work. ~/.ssh/config entry is exactly the same. +[2020-05-10T19:04:48Z]jhassSuperLag: same debugging steps as before :) run ssh with -v and check it actually picks up the key. Fetch the keys github knows from github.com/youruser.keys, put them in files and run ssh-keygen -l on each. Check the fingerprint shown by ssh -v matches at least one of these ssh-keygen -l outputs
message no. 180403
Posted by jhass in #github at 2020-05-10T11:12:15Z
even manually that one copy paste doesn't seem like that much extra work
+[2020-05-11T04:48:50Z]white_shadowI have been invited to a private repo but after accepting the invitation it is redirecting me to 404 error page, what could be the issue in this case? +[2020-05-11T16:18:37Z]oxekHow long do I need to wait for "There have been several failed attempts to sign in... Please wait a while and try again later." to go away so that I can login? +[2020-05-11T16:18:56Z]oxekI use a TOTP client so that block should not have even happened +[2020-05-11T17:13:06Z]hedayHi all, I did a git clone to a repo and did some work on it locally. later on, realized i can't push those changes. Now I forked the repo in my git account. How do I push into my fork? +[2020-05-11T17:14:28Z]R2robotset the remote