github-starred/gitea-mirror
2
0
Fork 0
mirror of https://github.com/RayLabsHQ/gitea-mirror.git synced 2026-05-21 15:11:22 -05:00
Code Issues 140 Packages Projects Releases 100 Wiki Activity

[PR #177] [MERGED] Support release limits above 100 #2071

New Issue
Closed
opened 2026-05-03 03:02:48 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-05-03 03:02:48 -05:00
Owner
Copy Link

📋 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)

  • 9bc7bbe Support 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

  • 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

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/RayLabsHQ/gitea-mirror/pull/177 **Author:** [@arunavo4](https://github.com/arunavo4) **Created:** 2/24/2026 **Status:** ✅ Merged **Merged:** 2/24/2026 **Merged by:** [@arunavo4](https://github.com/arunavo4) **Base:** `main` ← **Head:** `codex/issue-176` --- ### 📝 Commits (1) - [`9bc7bbe`](https://github.com/RayLabsHQ/gitea-mirror/commit/9bc7bbe33f4ec7b4c60ea00b7e7a16d16af72a28) Support release limits above 100 ### 📊 Changes **2 files changed** (+39 additions, -15 deletions) <details> <summary>View changed files</summary> 📝 `src/components/config/GitHubMirrorSettings.tsx` (+2 -3) 📝 `src/lib/gitea.ts` (+37 -12) </details> ### 📄 Description ## 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 --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-05-03 03:02:48 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
enhancement
help wanted
pull-request
Mirrored from GitHub Pull Request
 question
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea-mirror#2071
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?