How do you use token to access github in a basic terminal?
-
So I put all of my important dot files on Github. Whenever I need to reinstall stuff, I pull the files. To get this working, I need to do the "gh auth login" where it grants the ssh key. Or I can create a token for that specific machine on Github. This is a long list of letters/numbers that I then copy when doing "git clone".
During installations of Arch or even a minimal Debian, how do you do this? There are no browsers, so the command "gh auth login" would get stuck.
Is there a better way to do this, other than making the dotfiles repo public?
-
System shared this topic on
-
So I put all of my important dot files on Github. Whenever I need to reinstall stuff, I pull the files. To get this working, I need to do the "gh auth login" where it grants the ssh key. Or I can create a token for that specific machine on Github. This is a long list of letters/numbers that I then copy when doing "git clone".
During installations of Arch or even a minimal Debian, how do you do this? There are no browsers, so the command "gh auth login" would get stuck.
Is there a better way to do this, other than making the dotfiles repo public?
Maybe you could go to:
Settings > Developer Settings > Personal Access Tokens > Tokens (Classic)
And then create a new token there.
Then you should be able to clone a private repo as long as you have
gitinstalled.When you
git cloneyour private repo,gitwill ask for your username, enter that. Then it's gonna ask for your password. Don't enter your GitHub password. Enter your token.Clone should work.
-
Maybe you could go to:
Settings > Developer Settings > Personal Access Tokens > Tokens (Classic)
And then create a new token there.
Then you should be able to clone a private repo as long as you have
gitinstalled.When you
git cloneyour private repo,gitwill ask for your username, enter that. Then it's gonna ask for your password. Don't enter your GitHub password. Enter your token.Clone should work.
Yes, PSK will work.
-
So I put all of my important dot files on Github. Whenever I need to reinstall stuff, I pull the files. To get this working, I need to do the "gh auth login" where it grants the ssh key. Or I can create a token for that specific machine on Github. This is a long list of letters/numbers that I then copy when doing "git clone".
During installations of Arch or even a minimal Debian, how do you do this? There are no browsers, so the command "gh auth login" would get stuck.
Is there a better way to do this, other than making the dotfiles repo public?
You can use your token with the REST api. And use that to do whatever you want.
you can also use your token for
git clonelike so:$ git clone https:/git:[email protected]/myown/repo -
You can use your token with the REST api. And use that to do whatever you want.
you can also use your token for
git clonelike so:$ git clone https:/git:[email protected]/myown/repoBest practice is not to use raw credentials on the command line because it exposes them in process listings and shell history files.
-
So I put all of my important dot files on Github. Whenever I need to reinstall stuff, I pull the files. To get this working, I need to do the "gh auth login" where it grants the ssh key. Or I can create a token for that specific machine on Github. This is a long list of letters/numbers that I then copy when doing "git clone".
During installations of Arch or even a minimal Debian, how do you do this? There are no browsers, so the command "gh auth login" would get stuck.
Is there a better way to do this, other than making the dotfiles repo public?
Just use SSH keys.
And use SSH urls (git@....) instead of HTTPS urls (https://...) when cloning.
-
So I put all of my important dot files on Github. Whenever I need to reinstall stuff, I pull the files. To get this working, I need to do the "gh auth login" where it grants the ssh key. Or I can create a token for that specific machine on Github. This is a long list of letters/numbers that I then copy when doing "git clone".
During installations of Arch or even a minimal Debian, how do you do this? There are no browsers, so the command "gh auth login" would get stuck.
Is there a better way to do this, other than making the dotfiles repo public?
Personally I find git-credential-manager much easier to use.
It manages Oauth2 for you.
Or ssh keys.
-
System shared this topic on
