From f916f12b9067f13c57795388fc33fd095d620c35 Mon Sep 17 00:00:00 2001 From: S Date: Sun, 1 Mar 2026 11:08:33 -0500 Subject: [PATCH] =?UTF-8?q?docs:=20update=20gitea-api.md=20=E2=80=94=20rem?= =?UTF-8?q?ove=20hardcoded=203-repo=20pagination=20assumption?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Claude Opus 4.6 --- contracts/gitea-api.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/contracts/gitea-api.md b/contracts/gitea-api.md index 9b87ed0..c537242 100644 --- a/contracts/gitea-api.md +++ b/contracts/gitea-api.md @@ -572,7 +572,7 @@ GitHub errors return JSON with `message` and optionally `errors`: ## Pagination Gitea list endpoints return paginated results. The migration scripts do NOT -paginate because the data volumes are small (3 repos, ~3 runners, ~3 mirrors). +paginate because the data volumes are typically small (a handful of repos, runners, and mirrors). ### Gitea Pagination Headers @@ -593,6 +593,6 @@ link: ; rel="next", ; rel="last" ### When Pagination Would Matter If any of these grow beyond 50 items, scripts that use these endpoints would -silently miss results. For this migration (3 repos, handful of runners), this -is not a concern. If extending to N repos where N > 50, add `?limit=N` or +silently miss results. For typical migrations (under 50 repos/runners), this +is not a concern. If migrating more than 50 repos, add `?limit=N` or implement `Link` header following.