Each package that uses Ghub uses its own token. Despite that, chances are good that after successfully configuring one package you can just start using another package pretty much instantly.
If the necessary token to access a Github instance is not available when a package makes an API request, then a setup wizard pops up, and after answering a few questions you are good to go. Even the request that caused the wizard to be summoned should succeed and for most users this should be true even when configuring the very first token.
However, in some situations some manual configuration is necessary before using the wizard, or the wizard cannot be used at all:
github.host. You also have to tell Ghub your username for that instance using the variable
github.HOST.usereven if it is the same as on Github.com.
github.HOST.userfor an Enterprise instance) is unset when the wizard is first summoned, then you are asked to provide your username. That value is then stored globally to avoid having to ask you that question once per repository. If you have multiple accounts on Github.com (or a Github Enterprise instance), then you have to explicitly tell Ghub about that. This can be done by setting the repository-local values of the appropriate variable before the wizard is invoked.
The variables mentioned above — and others — are documented in Configuration Variables and the setup wizard is documented in Interactively Creating and Storing a Token.
|• Setting the Username:|
|• Interactively Creating and Storing a Token:|
|• Manually Creating and Storing a Token:|
|• How Ghub uses Auth-Source:|