Describe the bug

The title says it all.
gh version 0.9.0 (2020-05-26)

Steps to reproduce the behavior

1. Create a personal access token with admin:org, admin:public_key, gist, and repo scopes.

2. On my local machine, run this command:

    gh config set -h github.com oauth_token MYTOKEN
   

3. Use the cli to clone a repo:

$ gh repo clone supabase/supabase

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`