We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
gh auth login --with-token
gh auth login --with-token is described to accept a token on standard input. The usage example in the docs is
gh auth login --with-token < mytoken.txt
However, if I don't provide a token file using the redirect operator, the command gh auth login --with-token hangs.
gh auth logout
It isn't terribly clear what behavior is expected, here, but it seems like an interactive prompt for where to find the token may have been intended. However, that code seems unreachable given the conditional above it, and no implementation exists to prompt for a token when one isn't provided.
I would expect to be prompted for the token OR the token's file location if one wasn't provided using a redirect operator.
Describe the bug
gh auth login --with-tokenis described to accept a token on standard input. The usage example in the docs isgh auth login --with-token < mytoken.txtHowever, if I don't provide a token file using the redirect operator, the command
gh auth login --with-tokenhangs.Steps to reproduce the behavior
gh auth logoutgh auth login --with-tokenExpected vs actual behavior
It isn't terribly clear what behavior is expected, here, but it seems like an interactive prompt for where to find the token may have been intended. However, that code seems unreachable given the conditional above it, and no implementation exists to prompt for a token when one isn't provided.
I would expect to be prompted for the token OR the token's file location if one wasn't provided using a redirect operator.