[Schema Inaccuracy] (GHES 3.18) organization_copilot_seat_management property on the app-permissions schema is missing read
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 75/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- openapi
- Domain
- api
Research direction
Locate the app-permissions schema used by the organization installations endpoint and inspect the organization_copilot_seat_management property. Compare it with the documented GHES 3.18 response example, add the missing valid value, and run the repository's schema validation or relevant tests to confirm the response is representable.
Written by the indexing model from the issue text.
Description
Schema Inaccuracy
The organization_copilot_seat_management property on the app-permissions schema is missing read from its enum values for GHES 3.18.
Expected
The organization_copilot_seat_management property on the app-permissions schema should include read as a valid enum value:
"organization_copilot_seat_management": {
"type": "string",
"enum": ["read", "write"]
}
Currently the schema only lists:
"organization_copilot_seat_management": {
"type": "string",
"enum": ["write"]
}
Reproduction Steps
List app installations for an organization that has GitHub Copilot Business. Some installations will have
"organization_copilot_seat_management": "read" in their permissions object, which is not representable by the current schema.
curl -H "Authorization: Bearer $GITHUB_TOKEN" \
-H "Accept: application/vnd.github+json" \
https://ghes.example.com/api/v3/orgs/{org}/installations
Example response snippet:
{
"installations": [
{
"permissions": {
"organization_copilot_seat_management": "read"
}
}
]
}
- Dominant language
- No language data
- Stars
- 1.6k
- Forks
- 342
- Avg merge
- 3h 33m
- Merged PRs (30d)
- 51
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from github/rest-api-description
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
github/rest-api-description#7201 ·
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
github/rest-api-description#7163 ·
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
github/rest-api-description#7162 ·
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
github/rest-api-description#7135 ·
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
github/rest-api-description#7111 · 1 comment ·
All issues in github/rest-api-description
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
kind/cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
kubernetes-sigs/kueue#15937 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·