Scope error in migrate-repo during CreateMigrationSource call
See original GitHub issueDescription
I’m getting a scope permission error during a call the GetMigrationSource, and either the error message is misleading or there’s a problem I can’t see.
[4:40 PM] [DEBUG] RESPONSE (OK): {"data":{"createMigrationSource":null},"errors":[{"type":"FORBIDDEN","path":["createMigrationSource"],"locations":[{"line":1,"column":109}],"message":"rbanks54 does not have the correct permissions to execute `CreateMigrationSource` query. It requires the following scopes: ['read:org', 'repo'], but the token has only been granted the: ['read:org', 'repo'] scopes. Please modify your token's scopes at: https://github.com/settings/tokens."}]}
The token needs ['read:org', 'repo'], and has ['read:org', 'repo'], yet an error is thrown.
Reproduction Steps
> gh --version gh version 2.17.0 (2022-10-04) > gh ado2gh --version [4:46 PM] [INFO] You are running the latest version of the ado2gh CLI [v0.29] 0.29
- Set the ADO_PAT, and GH_PAT environment variables
- execute
gh ado2gh migrate-repo --ado-org "<AzDO>" --ado-team-project "<PROJ>" --ado-repo "<AzDO-Repo>" --github-org "<GH>" --github-repo "<GH-Repo>" --wait --verbose
Issue Analytics
- State:
- Created a year ago
- Comments:9 (1 by maintainers)
Top Results From Across the Web
Receiving a GraphQL error from `createMigrationSource ...
When running gh gei migrate-repo , if the GraphQL createMigrationSource mutation responds with a 200 OK with a GraphQL error, e.g.:.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
⏫ FYI to any readers, this is now being handled as a support ticket since it doesn’t appear to be an issue with the CLI specifically
Thanks @rbanks54 🤝 If you could file a support ticket, that would be great. Sure we can take a look and figure out what’s going on here.