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.
**Original Pull Request:** https://github.com/RayLabsHQ/gitea-mirror/pull/177
**State:** closed
**Merged:** Yes
---
## 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.
Closes #176
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.
Original Pull Request: https://github.com/RayLabsHQ/gitea-mirror/pull/177
State: closed
Merged: Yes
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