Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

No "Copilot Requests" permission in GitHub Apps despite the Copilot SDK documentation saying otherwise

Open
#2,304 8 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
github

Research direction

Start with the linked Server-to-server authentication page, especially the “Other services and CI systems” section, and compare its Copilot Requests permission guidance with the GitHub App creation UI. Review the related Copilot SDK authentication documentation and support ticket context to establish the expected behavior. Done means the documentation and GitHub App permissions agree, with the customer-facing discrepancy addressed.

Written by the indexing model from the issue text.

Description

documentation support-escalation support-sev2

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).

  • sev1 - Engineering must respond, when paged, within 1 business day
  • sev2 - Engineering must respond to this issue within 2 business days
  • sev3 - Engineering must respond to this issue within 2 business days

Service

copilot-sdk

Context

⚠️ Kindly provide all the requested information to ensure a prompt and efficient response. ⚠️

GitHub Support Plan

  • Top 20
  • Premium Plus
  • Premium
  • Enterprise
  • Free/Pro/Team

GitHub Product(s) Impacted (check appropriate boxes and provide GHES version if applicable)

  • GitHub.com (including GHEC)
  • GitHub Enterprise Server.
    • Running version: x.y.z
    • Recently upgraded from version: x.y.z (upgrade date: yyyy-mm-dd)
  • Proxima (ghe.com)
    • Customer tenant: -

Customer Impact

If applicable, list the impacted entities:

  • Enterprise: -
  • Organization: -
  • Repository: -
  • User: -

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:

  1. Go to ...
  2. Click on ...
  3. Scroll down to ...
  4. 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

Dominant language
Java
Stars
10.5k
Forks
1.5k
Avg merge
1d 9h
Merged PRs (30d)
130

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/copilot-sdk

All issues in github/copilot-sdk

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.