Summary - remove the UI hard cap of 100 releases in release limit input
add paginated GitHub release fetching so configured limits above 100 are respected
preserve existing behavior/order processing for release mirroring
Why
Issue #176 reported that release limit appears capped at 100. The previous implementation used a single API call and UI clamp, which prevented higher values from being effective.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/RayLabsHQ/gitea-mirror/pull/177
Author: @arunavo4
Created: 2/24/2026
Status: ✅ Merged
Merged: 2/24/2026
Merged by: @arunavo4
Base:
main← Head:codex/issue-176📝 Commits (1)
9bc7bbeSupport release limits above 100📊 Changes
2 files changed (+39 additions, -15 deletions)
View changed files
📝
src/components/config/GitHubMirrorSettings.tsx(+2 -3)📝
src/lib/gitea.ts(+37 -12)📄 Description
Summary - remove the UI hard cap of 100 releases in release limit input
Why
Issue #176 reported that release limit appears capped at 100. The previous implementation used a single API call and UI clamp, which prevented higher values from being effective.
Closes #176
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.