Skip to content

gh warns me that it requires read:org OAuth scope #1026

Description

@chmaynard

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`

Activity

  1. changed the title [-]gh warns me that it requires read:org OAuth scope. My token already has it.[/-] [+]gh warns me that it requires read:org OAuth scope but my token already has it.[/+] on May 27, 2020
  2. changed the title [-]gh warns me that it requires read:org OAuth scope but my token already has it.[/-] [+]gh warns me that it requires read:org OAuth scope[/+] on May 27, 2020
  3. mislav commented on May 28, 2020

    @mislav
    Contributor

    Thanks for reporting! It looks like that in #786 it slipped my mind to treat admin:org as inclusive of read:org.

  4. self-assigned this
    on May 28, 2020
  5. David-Botos commented on Jun 9, 2024

    @David-Botos

    I was wondering if you could explain why read:org permissions are necessary to use cli tools (version gh version (2.50.0 (2024-05-29)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions