Models Permissions For Github Apps not documented #194340
Replies: 1 comment
|
Hi @sajalverma17! 👋 That definitely looks like a documentation oversight on GitHub's end. It's common for new features or permissions UI elements to get pushed live before the corresponding anchor links are fully updated in the public docs. Since you are setting up a GitHub App with the new Models permission, here is the basic workflow framework you would use to handle this while the docs catch up: 1.Verify App Scope: Ensure the permission is set to Read-only (or Read/Write if available) under your GitHub App's Permissions & events > Organization permissions. 2.Generate Installation Token: Use your App's private key to authenticate and request an installation access token specifically scoped for that organization. 3.Test the Endpoint: Since the exact REST/GraphQL API paths for "Models" aren't listed in that specific section yet, try calling the organization-level models endpoint using your installation token to verify access. 4.Monitor API Headers: Check the response headers (X-Accepted-OAuth-Scopes or X-OAuth-Scopes) during your test calls to confirm exactly what string GitHub's backend expects for this permission. |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Question
💬 Feature/Topic Area
Models
Body
I noticed this when I was enabling Models permissions for my Github App, and I clicked the
Learn Morelink:It takes me here: https://docs.github.com/en/rest/authentication/permissions-required-for-github-apps#organization-permissions-for-models
However, the
#organization-permissions-for-modelsis not a section yet added to Permissions required for Github Apps documentation page. Looks like the documentation is missing.All reactions