You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @purplefishies. Re-authenticating will be made easier once #225 ships. However, if you want to switch between 2 user accounts, I don't think you'll want to re-authenticate with your username and password every time.
A feature has just landed in master where you can define GITHUB_TOKEN as your environment variable and put your Personal Access Token in there. So when you switch between users, all you have to do is make your script switch out the value of this environment variable. Hub's API requests will be done using that token for the corresponding user and ignore the user config set in ~/.config/hub.
This hasn't been released yet, but just letting you know. Will that be enough?
If I use a single computer to commit as two different people to two different GitHub accounts, I can do this by changing my email identity using
git config --local --set user.email=[email protected]
Then I can commit this code and after doing the whole remote add , then I can push to a GitHub repo as this different email user.
I cannot do this using hub however because if I perform a
it uses the USERNAME stored in ~/.config/hub
I can't find a well documented way to fix this using the hub command line tool.
The text was updated successfully, but these errors were encountered: