fix(project): suggest 'project' scope instead of 'read:project'#12601
Closed
fix(project): suggest 'project' scope instead of 'read:project'#12601
Conversation
Member
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR fixes #12585.
Problem: Users receive a confusing error loop when attempting to view projects without sufficient scopes. The CLI suggests adding
read:project, but upon doing so, the operation fails again requiring project (write access), leading to a frustrating double-auth cycle.Solution: The error handling logic now detects when
read:projectis the missing scope and proactively suggests the broader project scope instead. This ensures users get the necessary permissions in a single step.Technical Details
go test ./pkg/cmd/project/shared/queriesChanges Made
read:projectand upgrade the suggestion to project.Quality Checklist