Can't push yet again #66905
Replies: 2 comments
-
The error message you're seeing indicates that GitHub has removed support for password authentication when pushing to repositories over HTTPS. Instead, they now recommend using a personal access token for authentication. To fix this issue and push to your repository, you need to update your Git configuration to use a personal access token. Here are the steps to fix this issue:
This should resolve the authentication issue, and you should be able to push to your GitHub repository using the personal access token. Remember to keep your personal access token secure and do not share it publicly, as it provides access to your GitHub account and repositories. |
Beta Was this translation helpful? Give feedback.
-
Maybe I wasn't clear. When I said I regenerated my expired token that means I already have a token. git config --global credential.helper store does nothing and goes back to prompt. git pull then says:
If you wish to set tracking information for this branch you can do so with:
There is no tracking information for the current branch.
If you wish to set tracking information for this branch you can do so with:
git branch
my branch is called 'main'. $ git branch --set-upstream-to=origin/main main |
Beta Was this translation helpful? Give feedback.
-
remote: Support for password authentication was removed on August 13, 2021.
remote: Please see https://docs.github.com/en/get-started/getting-started-with-git/about-remote-repositories#cloning-with-https-urls for information on currently recommended modes of authentication.
Same old thing we've seen many times, so tired of seeing it. I've been able to push for a while then my token expired so I regenerated it now can't push. How can I fix this?
Beta Was this translation helpful? Give feedback.
All reactions