Repository navigation
Conversation
setCommitsAuto walked every page of the org's repositories to find the one matching the git remote, which is hundreds of requests for orgs with thousands of repositories. Pass the remote name as the endpoint's `query` filter and keep the exact match on the client. When the filtered lookup is empty, check for any repository so the no-integration fallback still works. Co-Authored-By: Claude Opus 5.5 <[email protected]>
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
BYK
approved these changes
Oct 17, 2026
| const endpoint = `organizations/${orgSlug}/releases/${encodeURIComponent(version)}/`; | ||
| throw new ApiError( | ||
| NO_REPO_INTEGRATIONS_MESSAGE, | ||
| 400, |
Member
There was a problem hiding this comment.
This should be a 404, right? 400 usually indicates incorrect inputs etc.
BYK
marked this pull request as ready for review
October 17, 2026 23:26
The client-side "no repository integrations" error used status 400, which error reporting and isUserError treat as a CLI bug. Use 404 so it's classified as a user error, and match it in the set-commits fallback. Co-Authored-By: Claude Opus 5.5 <[email protected]>
This branch was previously deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
set-commits --autowalks every page of the org's repositories to find the one matching the git remote. The repos endpoint sorts by name with offset pagination and counts hits, so each page reads and sorts every repository in the org. Orgs with tens of thousands of repositories make hundreds of requests per run at hundreds of milliseconds each./organizations/{org}/repos/gets about 15M requests a week, nearly all fromset-commitsvia the bundler plugins and the release GitHub Action: ~700 hours of request time a week (92ms p50, 450ms p95) and ~85 hours of database time for the repo list query. Today that traffic comes from the Rust sentry-cli, which walks every page the same way.This passes the remote's name as
query(the endpoint's case-insensitive name filter) and keeps the exact match on the client, so it's usually one request. If the filtered lookup is empty, aper_page=1request checks whether the org has any repositories, so the "no repository integrations" fallback and cache still work. Servers that ignorequeryreturn every repository and the exact match still finds it.Also fixes the
setCommitsAutoJSDoc, which hadNO_REPO_INTEGRATIONS_MESSAGEinserted in the middle of it.