Open moorepants opened 4 years ago
We already do this for private repos so I guess we can migrate it. When will it be deprecated.
Personal access tokens are annoying because you have to create them and then delete them, unless there's a better way to do them now?
I use the tokens for other services and it seems you just need to keep one around for the api, I think.
I mean doctr creates and deletes them with the API (which uses the password API to do, so hopefully doing that will stay supported). It's just annoying because if it gets interrupted before the delete the token will still be there. And GitHub also sends you an email about it every time a token gets created, which is confusing.
I got this email that I think was related to a doctr configure call:
Hi @moorepants,
You recently used a password to access an endpoint through the GitHub API using python-requests/2.22.0. We will deprecate basic authentication using password to this endpoint soon:
https://api.github.com/
We recommend using a personal access token (PAT) with the appropriate scope to access this endpoint instead. Visit https://github.com/settings/tokens for more information.
Thanks, The GitHub Team