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
When the command > gh auth login --with-token < token.txt is issued, it prompts for the authentication type. Clearly, if "--with-token" is present, the desire is to use the provided token value.
Steps to reproduce the behavior
Type this '.gh auth login --with-token < token.txt'
View the prompt for authentication type even tho it is supplied via the '--with-token' flag.
Expected vs actual behavior
When the authentication type is supplied, no prompt should be generated.
Logs
=> ERROR [ 7/12] RUN gh auth login --with-token < .githubtoken --scopes repo,read:org 0.2s
------
> [ 7/12] RUN gh auth login --with-token < .githubtoken --scopes repo,read:org:
? How would you like to authenticate GitHub CLI? [Use arrows to move, type to filter]
#10 0.201 > Login with a web browser
#10 0.201 Paste an authentication token
#10 0.201 could not prompt: EOF
------
executor failed running [/bin/sh -c gh auth login --with-token < .githubtoken --scopes repo,read:org]: exit code: 1
The text was updated successfully, but these errors were encountered:
That's fine. I think the difference is that this is a bug vs. an enhancement. For a dockerfile, I really need gh to provide a non-interactive authentication method.
Describe the bug
When the command > gh auth login --with-token < token.txt is issued, it prompts for the authentication type. Clearly, if "--with-token" is present, the desire is to use the provided token value.
Steps to reproduce the behavior
Expected vs actual behavior
When the authentication type is supplied, no prompt should be generated.
Logs
The text was updated successfully, but these errors were encountered: