fix(backend): stop Gitea/Forgejo pagination on empty page response (#1130)

* fix(backend): stop Gitea/Forgejo pagination on empty page response

When an API token can only see a subset of org repos, the x-total-count
header reports the org total while the token returns fewer items. The
previous loop condition (output.length < totalCount) would never be
satisfied for the visible subset, causing infinite pagination.

Now we break out of the loop when the API returns an empty page,
matching the Gitea API pagination docs recommendation.

Fixes #1108

Co-authored-by: Brendan Kellam <brendan-kellam@users.noreply.github.com>

* chore: add changelog entry for Gitea/Forgejo pagination fix

Co-authored-by: Brendan Kellam <brendan-kellam@users.noreply.github.com>

---------

Co-authored-by: claude[bot] <41898282+claude[bot]@users.noreply.github.com>
Co-authored-by: Brendan Kellam <brendan-kellam@users.noreply.github.com>

Author: brendan-kellam

CHANGELOG.md

@@ -9,6 +9,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Fixed
 - Fixed revision selection so the 64-revision cap prefers the newest matching branches and tags instead of pruning by ref-name order. [#1122](https://github.com/sourcebot-dev/sourcebot/pull/1122)
+- Fixed infinite pagination loop in Gitea/Forgejo when an API token can only see a subset of org repos (the `x-total-count` header reports org total while token returns fewer items). [#1130](https://github.com/sourcebot-dev/sourcebot/pull/1130)
 
 ## [4.16.11] - 2026-04-17
 

packages/backend/src/gitea.ts

@@ -254,6 +254,9 @@ const paginate = async <T>(request: (page: number) => Promise<HttpResponse<T[],
     while (output.length < totalCount) {
         page++;
         const result = await request(page);
+        if (result.data.length === 0) {
+            break;
+        }
         output.push(...result.data);
     }