4 ms·
I don't understand this. It says I need to begin using a "personal access token" and links here. https://docs.github.com/en/free-pro-team@latest/github/getting
by recursive 6y ago
I don't understand this. It says I need to begin using a "personal access token" and links here. https://docs.github.com/en/free-pro-team@latest/github/getting-started-with-github/set-up-git#next-steps-authenticating-with-github-from-git https://docs.github.com/en/free-pro-team@latest/github/getti...
The target document says nothing about any kind of tokens.
I'm just a regular guy with some github repos. Am I going to get locked out?
- tialaramex 6y agoYou won't get locked out. If you use the GitHub APIs (you probably don't as a "regular guy with some github repos") you need to adjust how you do that to use tokens. If you haven't adjusted before they get rid of the legacy authentication you'll have to manually log into your GitHub account and read up how to do it then or your API calls break. If you use HTTPS URLs to refer to your github repos (more likely on Windows) from Git then you need to get tokens by the deadline to make that work. Or, switch to using SSH URLs for your repositories if that seems easier. If, like a great many GitHub users, neither applies, you don't need to do anything, it will continue to work as before. As a rule of thumb, think about your GitHub password. Anywhere you have to keep typing that in (other than the actual GitHub sign in page) or you've saved it to be re-used over and over, that will stop working. That was always a bad idea, and now it will stop working.