"Proper" way to push to github from command line with an access token

Asked Aug 14 '21 at 13:06

Active Aug 15 '21 at 01:33

Viewed 229 times

Based on the changes to Github authetication starting yesterday, I am wondering what the "correct" way to push with access tokens is.

On Ubuntu 20 there isn't any macOS keychain like feature for managing tokens (that I know of).

Based on this post, Authenticate with GitHub using a token, many reponses suggest using git remote set-url https://username:$TOKEN@github.com/$ORG/$REPO, but doing this seems to store the token's value in plain text in .git/.

What then are the best practices for storing access tokens locally? Environment variables?

[Note by torek before closing: in this case the solution was this one.]

edited Aug 15 '21 at 01:33

torek

448,244
59
642
775

asked Aug 14 '21 at 13:06

Michael

(1) Might depend what operating system you're using. (2) Where's the programming in this question? – matt Aug 14 '21 at 13:10
I'm using ubuntu – Michael Aug 14 '21 at 13:11
Shouldn't that fact be in the question? – matt Aug 14 '21 at 13:11
If you are on Ubuntu (or any other Linux), it's probably better to drop https and use ssh instead, if possible. – snakecharmerb Aug 14 '21 at 13:14
1

See one of the many answers already given. For example start at https://stackoverflow.com/questions/68775869/support-for-password-authentication-was-removed-please-use-a-personal-access-to – matt Aug 14 '21 at 13:19
1

found a good fix from https://stackoverflow.com/a/68775982/11015015 – Michael Aug 14 '21 at 13:23

"Proper" way to push to github from command line with an access token

0 Answers0