I really appreciate all these suggestions! Unfortunately none of them have lead to success, although I've learned a few things.
Even after doing the unset credential.helper commands and creating a new remote, I get this: C:\repos\leo-editor>git push leo_origin_2 devel Username for 'https://github.com': tbpassin Password for 'https://[email protected]': remote: Permission to leo-editor/leo-editor.git denied to tbpassin. fatal: unable to access 'https://github.com/leo-editor/leo-editor.git/': The requested URL returned error: 403 That's to say, the very same thing I've gotten all along. I used my github user name and pw, the same ones I use to log into GitHub with. I get the same whether I push from GitHub Extensions using the Push menu item, or by directly running git in a Windows cmd window. Some things I've learned: If you use the https://github ... URL, then no private key is involved, so it doesn't matter if you created one and told putty to use it. You saw some github entries in the Windows Credentials Manager that you couldn't account for. I had them too. I discovered that after I had deleted them all, then the next time I tried to push to upstream that a new such entry had been created, with the user name being <Personal Identification Token>. In the GitHub page that shows your personal tokens, I saw that a new one had been created. There's no way to find out the actual value of that token, but git seems to know. After I ran the unset credential.helper commands, I always got a username/pw dialog (as you did), and these credential entries didn't get added. So that's all interesting but didn't get me connected. I wonder if the Leo repo just doesn't have me marked as being able to push? On Monday, April 20, 2020 at 4:20:31 PM UTC-4, Matt Wilkie wrote: > > Hmm, I wonder if that could be my Windows firewall preventing the outbound >> connection because it's ssh? >> > > I get the same error, but I'm not using Putty/ssh to connect and don't > have any keys loaded. > > As I understand it (and I'm not sure I do understand it!) there 3 common > pathways on Windows for git authentication: > > - Putty and SSH keys > - Windows Credentials (example below) > - OAuth tokens (in Git Extensions see "Plugins>>Github" menu) > > I think it is possible to be have all 3 configured at once on a single > machine, but only using one at any given moment, through means opaque to me. > > On my main Leo computer going to "Control Panel\User Accounts\Credential > Manager >> Windows Credentials >> Generic" shows 2 github entries. I don't > know how these got setup initially, but I know on my work computer I was > able to add a github entry manually and that after that I could push. > Here's where I learned about Credential Manager: > https://github.com/gitextensions/gitextensions/issues/4916 > > > > For my work computer troubles I took the step of resetting my credentials > and now enter my password every time. Painful but alway works. > > Clearing stored git username and passwords > > > > elevate git config --system --unset credential.helper > > git config --global --unset credential.helper > > > > then for each repo: > > > git config --unset credential.helper > > > (*elevate *refers to https://code.kliu.org/misc/elevate/) > > > And then go to "Control Panel\User Accounts\Credential Manager" >> Windows > Credentials >> Generic" and remove the GitHub entries. > > After this using "git push" in console asked for credentials -- every time > though. Still need to figure out how to safely save them for re-use on this > machine. > > So, a bunch info, some of which may even be useful. > > Sign me, > > *a-reluctant-git-user-who-resents-the-amount-time-required-for-stupid-git-administrivia* > -matt > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/df950f33-86f4-4284-9597-a01ec66f2387%40googlegroups.com.
