privacy-in-design/gitea-migration
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: update gitea-api.md — remove hardcoded 3-repo pagination assumption

Browse Source 
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
S
2026-03-01 11:08:33 -05:00
parent e737128028
commit f916f12b90
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
contracts/gitea-api.md
View File

@@ -572,7 +572,7 @@ GitHub errors return JSON with `message` and optionally `errors`:
## Pagination ## Pagination
Gitea list endpoints return paginated results. The migration scripts do NOT 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 ### Gitea Pagination Headers
@@ -593,6 +593,6 @@ link: <url?page=2&limit=50>; rel="next", <url?page=5&limit=50>; rel="last"
### When Pagination Would Matter ### When Pagination Would Matter
If any of these grow beyond 50 items, scripts that use these endpoints would 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 silently miss results. For typical migrations (under 50 repos/runners), this
is not a concern. If extending to N repos where N > 50, add `?limit=N` or is not a concern. If migrating more than 50 repos, add `?limit=N` or
implement `Link` header following. implement `Link` header following.