Repository navigation
Commands that interact with classic projects should continue to work in the absence of GitHub App Installation Access Token repository projects permission #10714
Description
Activity
- changed the title
[-]Commands that interact with classic projects should continue to work in the absence of FGP repository projects permission[/-][+]Commands that interact with classic projects should continue to work in the absence of Fine Grained Token repository projects permission[/+]on Apr 2, 2025 - changed the title
[-]Commands that interact with classic projects should continue to work in the absence of Fine Grained Token repository projects permission[/-][+]Commands that interact with classic projects should continue to work in the absence of GitHub App Installation Access Token repository projects permission[/+]on Apr 2, 2025 #10942 should be the last PR in delivering this 🤞
I believe that this is now complete with
view / create /editbeing addressed to the best of my knowledge onissueandprcommands. I'm not aware of any other commands that requestprojectCardsorprojectsby default, but as with all this kind of work, tracking down the usage is not always so easy.
Description
In preparation for sunsetting the projects v1 API, the Fine Grained Token permissions on GitHub app were removed from the UI, which resulted in failures for commands that use
projectCardsin GQL queries (issue/pr create,issue/pr edit,issue/pr view), with newly generated tokens.We should modify the CLI so that it continues to work after they remove this, because it's not a good situation for the owning team to continue exposing this token that isn't used for anything.
Acceptance Criteria
Given I am targeting a host that has sunset v1 projects
And Given I have a token that doesn't have Fine Grained Permission for repository projects
When I run commands that currently interact with v1 projects
Then they do not fail horribly with
GraphQL: Resource not accessible by integration (repository.pullRequest.projectCards.nodes)Notes
This does not affect cases in which the user has used the
--jsonflag, orgh api.The implementation for this may simply be removing requests for
projectCardsandprojectsfor non-enterprise servers.Probably use trunk...cli-9430