GitHub Community
Token Authentication Requirement for Git Operations #23919
-
|
Today is August 14, 2021. I was working on a very important long-term project and I used the command Basically I am using VSCode to execute my Git operations. So when I look over to the blog mentioned in the error message, I found that I need to use token authentication for Git operations instead of password authentication.
 Token authentication requirements for Git operations | The GitHub BlogBeginning August 13th, 2021, we will no longer accept account passwords when authenticating Git operations on GitHub.com. Est. reading time: 3 minutes I am kind of afraid how to overcome this issue as because this is a very important project I am working on and I don’t want to loose any of my previous code commits. May I have your kind support of how to overcome this issue and switch from password authentication to token authentication without disrupting my codebase? Thank you. |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments
-
|
You need to create Create a PAT as described in the blog post, and use that instead of your password for pushing (or other authenticated Git operations). If the password is cached somewhere, you might need to delete that. The PAT should probably have the repo and workflow scopes. The first gives access to all your repositories, the second lets you modify GitHub Actions workflows. |
Beta Was this translation helpful? Give feedback.
-
|
Hi Luna, Thank you for your response to my problem. I finally solved my issue. Thanking you once again. |
Beta Was this translation helpful? Give feedback.
-
|
As best I can understand the PAT installation process described, I’ve followed the same process on two different linux systems. On one, everything works as expected. On the other, I am blocked from using https operations. Output from As airtower writes, it may be a caching issue. But I have no idea how to clear the cache. Are there other git config settings I’ve missed? Why else might one system work and not the other? I appreciate any specific steps to take to diagnose or resolve the problem. Thanks. |
Beta Was this translation helpful? Give feedback.
-
|
I am using Mac OS, and I successfully solved my issue using Keychain Access. |
Beta Was this translation helpful? Give feedback.
You need to create Create a PAT as described in the blog post, and use that instead of your password for pushing (or other authenticated Git operations). If the password is cached somewhere, you might need to delete that.
The PAT should probably have the repo and workflow scopes. The first gives access to all your repositories, the second lets you modify GitHub Actions workflows.