-
Notifications
You must be signed in to change notification settings - Fork 7.8k
Open
Labels
bugSomething isn't workingSomething isn't workingcoreThis issue is not accepting PRs from outside contributorsThis issue is not accepting PRs from outside contributorsgh-authrelating to the gh auth commandrelating to the gh auth commandneeds-designAn engineering task needs design to proceedAn engineering task needs design to proceed
Description
Describe the bug
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.txtHowever, if I don't provide a token file using the redirect operator, the command gh auth login --with-token hangs.
Steps to reproduce the behavior
- Logout of github in the CLI using
gh auth logout - Run
gh auth login --with-token - See that the terminal hangs
Expected 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.
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingcoreThis issue is not accepting PRs from outside contributorsThis issue is not accepting PRs from outside contributorsgh-authrelating to the gh auth commandrelating to the gh auth commandneeds-designAn engineering task needs design to proceedAn engineering task needs design to proceed