3 ms·
Thanks, but... something's off, and the error message makes no sense: $ git remote set-url origin git://<my userid>:<my token>@github.com/<repository owner's
by generationP 5y ago
Thanks, but... something's off, and the error message makes no sense:
$ git remote set-url origin git://<my userid>:<my token>@github.com/<repository owner's userid>/<repository name>
$ git pull
fatal: unable to look up <my userid>:<my token>@github.com (port 9418) (Non-recoverable failure in name resolution)
In other news, did I mention that the scopes are a bit confusing? I've checked "repo" and nothing else, based on the empirical assumption that the stuff near the top is the most important, but why don't I need, say, "read:public_key", if I am to use ssh?
(The set-url worked fine -- the new URL is indeed in the .git/config.)
- vtbassmatt 5y agoUsing username/PAT works with https:// https://, not git://. An easier route might be GCM Core (https://github.com/microsoft/Git-Credential-Manager-Core https://github.com/microsoft/Git-Credential-Manager-Core). And of course, disclosure, I'm the product manager for GCM Core and author of this blog post.
- generationP 5y agoThank you! The https solved the problem. I'll keep your manager in mind for when I need multi-factor auth, which so far hasn't happened.
- arthurcolle 5y agoSorry about that - was doing it from memory. Apologies, glad you got it fixed.
- arthurcolle 5y agoI'll check this out, thanks for the recommendation.