How to use GitHub token system across different computers?

I have a private repository at GitHub, which I need to access using SVN from many different computers.

Until recently, I could just do svn co https://github.com/username/reponame.git --username <githubuser>, and it would ask me for my password. I could do this on any computer out there, and it would just work.

Now that GitHub enforces the use of their new token system instead of good old passwords, I can still run the above command, and use a token as the password. However, as far as I can tell, I need to create a separate token for every single computer. I may also have to recreate the tokens after they expire. This seems like a major regression, but maybe I just do not to understand how to work efficiently with the GitHub token system.

Therefore, my question is: how can I use the GitHub in the same way as before, i.e., without having to create, recreate and manage tokens for the many computers I am working with? Basically, all I want is one token/password/whatever that works across all my machines.

Tokens aren’t bound to a specific computer, you can use them anywhere.

You can create tokens that don’t expire. There’s a security tradeoff: Unlimited tokens are more convenient, but if they get stolen the potential harm is greater because whoever has them can use them until you notice something is off and revoke the token.

As mentioned above you can use one token across as many machines as you like. If all you want to do is push/fetch using Git, having one token with repo and workflow scopes should be good. If you also use the GitHub API and have separate purposes (as in, needing different scopes) it’s good to have multiple tokens to reduce the possible damage in case one gets stolen.