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
The first time I run the hub command it prompts me for authentication, it then gets 403 because I have to enable SSO for my personal access token. This is fine if I'm just using the hub command in the terminal, but not very practical for large scripts that I have to share with my colleagues, because the first time they run it a script will fail.
It would be super handy if there was a hub login command that creates the token and then provides the link to enable SSO.
Equally it would be useful if hub commands waited for the user to click the link to enable SSO before continuing rather than exiting after receiving 403.
The text was updated successfully, but these errors were encountered:
It would be super handy if there was a hub login command that creates the token and then provides the link to enable SSO.
Equally it would be useful if hub commands waited for the user to click the link to enable SSO before continuing rather than exiting after receiving 403.
These are all great ideas. Thank you for suggesting!
The first time I run the hub command it prompts me for authentication, it then gets 403 because I have to enable SSO for my personal access token. This is fine if I'm just using the hub command in the terminal, but not very practical for large scripts that I have to share with my colleagues, because the first time they run it a script will fail.
It would be super handy if there was a
hub login
command that creates the token and then provides the link to enable SSO.Equally it would be useful if hub commands waited for the user to click the link to enable SSO before continuing rather than exiting after receiving 403.
The text was updated successfully, but these errors were encountered: