microsoft / microsoft/vscode-pull-request-github
Fetching pull request with query failed: HttpError: API rate limit exceeded
@alexr00 arbeitet bereits daran.
Seit 11.12.2025.
- Vorherrschende Sprache
- TypeScript
- Sterne
- 2.6k
- Forks
- 795
- Ø Merge
- 1 T. 4 Std.
- Gemergte PRs (30 T.)
- 46
Beschreibung
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:
- Create an issue in github.com
- Assign Copilot Coding Agent as assignee
- Let it finish its work
- Add review comments to the PR
- Letz it finish its work
- 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" } }
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Bewertung
Dieses Issue wurde noch nicht bewertet.