GitHub app: permission to access projectsV2 linked to repositories to which the user gave access permission?
#64849
Replies: 1 comment
-
|
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Question
Body
I have a question on permissions of GitHub apps:
When I install a GitHub app that I'm working on into my personal account (
installation.target_type: 'User'), and run the following GQL query, the repositories to which I gave access are being returned - but not theprojectsV2that are linked to those repositories:However, when I install the same GitHub app into an organisation (`installation.target_type: 'Organization'), and run the same query, the repositories and projects are returned, which is what I hope to achieve.
The app's
Organization permissionsincludesProjects, and theRepository permissionsincludeProjects, but that's labeled as "Manage classic projects within a repository." - that does not seem to includeProjectsV2, and there's no separate permission either.What am I overlooking? Is there a permission configuration that I'm missing to also get the user's repo's projects if the GitHub app is installed into a user account?
Beta Was this translation helpful? Give feedback.
All reactions