Uh oh!
There was an error while loading. Please reload this page.
perf(bitbucket): increase server page limit to 1000 - #981
Conversation
…repos Requests 1000 repos per page instead of defaulting to 25, reducing the number of API calls needed to enumerate large Bitbucket Server instances. The server silently caps at its configured maximum (page.max.repositories), so pagination via isLastPage/nextPageStart remains correct regardless. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This comment has been minimized.
This comment has been minimized.
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughIncreased Bitbucket Server paginated GET requests to include Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
…t 1000 Updates serverGetReposForProjects, getReposForAuthenticatedBitbucketServerUser, and getUserPermissionsForServerRepo to match the limit set in serverGetAllRepos. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Uh oh!
There was an error while loading. Please reload this page.
Summary
serverGetAllReposwas paginating in batches of 25 (the API default) when fetching all repos from Bitbucket Serverlimit: 1000per page, reducing the number of API round-trips for large instancespage.max.repositoriesmaximum (default 1000), so pagination viaisLastPage/nextPageStartremains correct regardless of the actual limit applied🤖 Generated with Claude Code
Summary by CodeRabbit