Using locate github

[Robert Moskowitz]

I have a F32 system I am using with github.  Yes, I know updating is 
overdue....

Github has switched to person access tokens since the last time I used 
it.  I created my https PAT but can't seem to get the git command to use 
it.  It just uses my GIt ID and password which now gets rejected.

Any recommendation (other than updating to F34!) to get my "git push 
origin" command to work?

It seems that there is a github-cli in beta, but does not seem to be an 
option here.

thanks

[Jonathan Billings]

On Fri, Sep 10, 2021 at 03:54:25PM -0400, Robert Moskowitz wrote:
> I have a F32 system I am using with github.  Yes, I know updating is
> overdue....
>
> Github has switched to person access tokens since the last time I used it.
> I created my https PAT but can't seem to get the git command to use
> it.  It just uses my Git ID and password which now gets rejected.
>
> Any recommendation (other than updating to F34!) to get my "git push origin"
> command to work?
>
> It seems that there is a github-cli in beta, but does not seem to be an
> option here.

Any reason why you can't add your ssh pubkey to github?  You'll need
to change your remote from the git URI to a ssh URI.

[Robert Moskowitz]

On 9/10/21 4:14 PM, Jonathan Billings wrote:
> On Fri, Sep 10, 2021 at 03:54:25PM -0400, Robert Moskowitz wrote:
> > I have a F32 system I am using with github.  Yes, I know updating is
> > overdue....
> >
> > Github has switched to person access tokens since the last time I used it.
> > I created my https PAT but can't seem to get the git command to use
> > it.  It just uses my Git ID and password which now gets rejected.
> >
> > Any recommendation (other than updating to F34!) to get my "git push origin"
> > command to work?
> >
> > It seems that there is a github-cli in beta, but does not seem to be an
> > option here.
>
> Any reason why you can't add your ssh pubkey to github?  You'll need
> to change your remote from the git URI to a ssh URI.

I will have to figure out how to make a ssh key for my github userid...

I will look into that.

Sigh.

I am guessing that in:

/home/rgm/data/htt/Projects/Critical/drafts/draft-ietf-drip-rid/.git

I change

[remote "origin"]
     url = https://github.com/ietf-wg-drip/draft-ietf-drip-rid
     fetch = +refs/heads/*:refs/remotes/origin/*

to use ssh: rather than https:

[Todd Zullinger]

Hi,

Robert Moskowitz wrote:
> On 9/10/21 4:14 PM, Jonathan Billings wrote:
> > Any reason why you can't add your ssh pubkey to github?  You'll need
> > to change your remote from the git URI to a ssh URI.
>
> I will have to figure out how to make a ssh key for my github userid...

At the risk of stating what you may already know, you don't
have to create a separate ssh key.

It's certainly not a bad idea to use different keys for
different systems, but it's not a requirement.
> I am guessing that in:
>
> /home/rgm/data/htt/Projects/Critical/drafts/draft-ietf-drip-rid/.git
>
> I change
>
> [remote "origin"]
>     url = https://github.com/ietf-wg-drip/draft-ietf-drip-rid
>     fetch = +refs/heads/*:refs/remotes/origin/*
>
> to use ssh: rather than https:

The easier way (I think) is to use the git remote command to
change the URL.  It's not just a search https and replace
with ssh, so you'll want to take the URL from the GitHub
web interface.  It'll typically be something like this:

[e-mail]:ietf-wg-drip/draft-ietf-drip-rid.git

To update that from the command line, you'd run:

git remote set-url origin [e-mail]:ietf-wg-drip/draft-ietf-drip-rid.git

I'd second Jonathan and suggest that ssh is the simpler way
to go, but it should be possible to use the "personal access
tokens" with the git from Fedora 32 (that was 2.26.3, IIRC).
The PAT is essentially just a password, so it ought to work
the same way as before.

You can make the storage of such logins pretty painless
using a git credential helper.  On Fedora, the libsecret
helper should work with both Gnome and KDE (and others if
they support the "Secret Service" API).

This is in the git-credential-libsecret package.  With that
installed, you should be able to enable it via:

git config credential.helper libsecret

That will enable it for the current repository.  (You can
enable it globally by adding --global after git config.)

Then you should be prompted for the username and password on
the next operation which requires it.  You'd use the PAT in
the password field and it should be stored in the Gnome
Keyring, KDE Wallet, or similar.

Having to type that out is one more reason I prefer using
ssh keys.  They're simpler to manage and useful in more
places.

HTH, and good luck on the overdue upgrade. :)