microsoft / microsoft/vscode-pull-request-github

Fetching pull request with query failed: HttpError: API rate limit exceeded

Open
#7,722 6 comments 5 reactions 1 assignee View on GitHub

@alexr00 is already working on this.

Since Dec 11, 2025.

info-needed
Dominant language
TypeScript
Stars
2.6k
Forks
795
Avg merge
1d 4h
Merged PRs (30d)
46

Description

I tried the Copilot Coding Agent for the first time today. After the second code review on a PR created by the coding agent, I hit this limit while commenting the changes. What is the issue?
The PR changed 17 files and contains 10 conversations with 1-2 comments.

  • Extension version: 0.116.2
  • VSCode Version: 1.103.2
  • OS: Windows 10
  • Repository Clone Configuration (single repository/fork of an upstream repository):
  • GitHub Product (GitHub.com/GitHub Enterprise version x.x.x):

Steps to Reproduce:

  1. Create an issue in github.com
  2. Assign Copilot Coding Agent as assignee
  3. Let it finish its work
  4. Add review comments to the PR
  5. Letz it finish its work
  6. Add comments again

Expected result:
User is able to continuous his code review via the vscode pull request extension

Determined result:
Exceeded the API rate limit and can't proceed the code review because of that

Rate limit request form the github API:
{ "resources": { "code_search": { "limit": 60, "remaining": 55, "reset": 1756589766, "used": 5, "resource": "code_search" }, "core": { "limit": 60, "remaining": 55, "reset": 1756589766, "used": 5, "resource": "core" }, "graphql": { "limit": 0, "remaining": 0, "reset": 1756590300, "used": 0, "resource": "graphql" }, "integration_manifest": { "limit": 5000, "remaining": 5000, "reset": 1756590300, "used": 0, "resource": "integration_manifest" }, "search": { "limit": 10, "remaining": 10, "reset": 1756586760, "used": 0, "resource": "search" } }, "rate": { "limit": 60, "remaining": 55, "reset": 1756589766, "used": 5, "resource": "core" } }

Contributor guide

No contributing guide indexed for this repository

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.