Warning - This might be a public repository, please be mindful of sharing sensitive data
Why are you seeing this issue?
This is a support escalation! You can find out more about expectations on communications and response times in the on-call docs. Thank you for doing your part to keep GitHub customers happy!
Severity
Note, for Sev1 issues always page the team first, using the PagerDuty information in the service catalog and the command .pager trigger N/A <reason>. Opening an issue for a Sev2 incident can come later (and can be done by the available Escalation Engineer).
Service
copilot-sdk
Context
⚠️ Kindly provide all the requested information to ensure a prompt and efficient response. ⚠️
GitHub Support Plan
GitHub Product(s) Impacted (check appropriate boxes and provide GHES version if applicable)
Customer Impact
If applicable, list the impacted entities:
Zendesk Ticket(s), support bundles, and other relevant Issues and links
Issue
Customer reports that while the Other services and CI systems section of the Server-to-server authentication page of the Copilot SDK documentation says you should:
Create a GitHub App with the Copilot Requests repository permission set to Read & write.
But when creating a GitHub App there doesn't seem to be any such repository permission in the UI.
To Reproduce
Steps to reproduce the behavior:
- Go to
...
- Click on
...
- Scroll down to
...
- See error
Expected behavior
The documented Read & write Copilot Requests repository permission should exist.
Screenshots
N/A
Additional context
I have tried creating a GitHub App myself and did not see this permission.
cc:
@patniko
Support Squad(s): @github/support-squad-ecosystem
Warning - This might be a public repository, please be mindful of sharing sensitive data
Why are you seeing this issue?
This is a support escalation! You can find out more about expectations on communications and response times in the on-call docs. Thank you for doing your part to keep GitHub customers happy!
Severity
Note, for Sev1 issues always page the team first, using the PagerDuty information in the service catalog and the command
.pager trigger N/A <reason>. Opening an issue for a Sev2 incident can come later (and can be done by the available Escalation Engineer).Service
copilot-sdk
Context
GitHub Support Plan
GitHub Product(s) Impacted (check appropriate boxes and provide GHES version if applicable)
Customer Impact
If applicable, list the impacted entities:
Zendesk Ticket(s), support bundles, and other relevant Issues and links
Issue
Customer reports that while the Other services and CI systems section of the Server-to-server authentication page of the Copilot SDK documentation says you should:
But when creating a GitHub App there doesn't seem to be any such repository permission in the UI.
To Reproduce
Steps to reproduce the behavior:
.........Expected behavior
The documented Read & write Copilot Requests repository permission should exist.
Screenshots
N/A
Additional context
I have tried creating a GitHub App myself and did not see this permission.
cc:
@patniko
Support Squad(s): @github/support-squad-ecosystem