Mislav Marohnić 3aaa231cc5 Guide user through re-authorization flow if read:org scope is missing ... How this works for people with existing OAuth tokens: $ gh issue list -L1 Notice: additional authorization required Press Enter to open github.com in your browser... [auth flow in the browser...] Authentication complete. Press Enter to continue... Showing 1 of 132 issues in cli/cli ... Users of Personal Access Tokens get a different notice: Warning: gh now requires the `read:org` OAuth scope. Visit https://github.com/settings/tokens and edit your token to enable `read:org` or generate a new token and paste it via `gh config set -h github.com oauth_token MYTOKEN`		2020-04-23 18:20:21 +02:00
..
cobrafish	Init slice with provided capacity if it's known in advance	2020-02-24 22:16:41 +01:00
config	Guide user through re-authorization flow if read:org scope is missing	2020-04-23 18:20:21 +02:00
ghrepo	move config stuff to its own package	2020-04-20 13:57:16 -05:00
run	move preparecmd and Runnable to its own package	2020-03-23 16:32:29 -05:00