github-authenticator

GitHub CLI authentication errors typically stem from expired tokens, incorrect credentials, or missing scopes. Run `gh auth status` to check your current login and token scopes, then use `gh auth refresh` to renew your token or `gh auth login` to re-authenticate with valid credentials.

Verify your GitHub CLI authentication status by running `gh auth status`. This command displays your logged-in username, host, and the scopes granted to your authentication token, confirming whether you're authenticated and what permissions you have.

Switch GitHub accounts by logging out of your current account with `gh auth logout`, then log in to another account using `gh auth login`. This process guides you through interactive authentication for the new account, useful for managing personal and work repositories separately.

Refresh your GitHub CLI token when `gh` commands fail with authentication errors, when your token expires, or after a long period of inactivity. Use `gh auth refresh` to renew your current credentials without fully re-logging in, restoring access to GitHub services.

Required scopes for GitHub CLI depend on your use case but typically include repository access and workflow permissions. Run `gh auth status` to view your current token's scopes, then `gh auth login` to request additional scopes if needed for your GitHub operations.

A 'Bad credentials' error in GitHub CLI indicates an invalid, expired, or insufficiently scoped authentication token. Use `gh auth status` to diagnose the issue, then either refresh your token with `gh auth refresh` or log in again with `gh auth login` to restore valid credentials.