github-starred/gitea-mirror
2
0
Fork 0
mirror of https://github.com/RayLabsHQ/gitea-mirror.git synced 2026-05-07 21:17:16 -05:00
Code Issues 103 Packages Projects Releases 93 Wiki Activity

[PR #180] [MERGED] Add one-click Re-run Metadata bulk action #1063

New Issue
Closed
opened 2026-04-19 13:38:17 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-19 13:38:17 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/RayLabsHQ/gitea-mirror/pull/180
Author: @arunavo4
Created: 2/24/2026
Status: ✅ Merged
Merged: 2/24/2026
Merged by: @arunavo4

Base: main ← Head: codex/issue-170-docs

📝 Commits (2)

  • f4074a3 Document metadata re-sync recovery steps
  • c340565 Add bulk re-run metadata action

📊 Changes

4 files changed (+234 additions, -0 deletions)

View changed files

📝 README.md (+14 -0)
📝 src/components/repositories/Repository.tsx (+91 -0)
➕ src/pages/api/job/reset-metadata.ts (+116 -0)
➕ src/types/reset-metadata.ts (+13 -0)

📄 Description

Summary

  • add a new bulk action in Repositories: Re-run Metadata
  • implement POST /api/job/reset-metadata to clear per-repo metadata state for selected repositories
  • after reset, immediately trigger Sync so metadata import runs again in one click
  • update README troubleshooting section with the UI-first recovery flow

Why

Addresses #170 with a simple UX path for recovering missed metadata after option changes, without adding complex runtime guards.

Test

  • bun test

🔄 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/180 **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-170-docs` --- ### 📝 Commits (2) - [`f4074a3`](https://github.com/RayLabsHQ/gitea-mirror/commit/f4074a37ad18f2594125f0c73e05568a9dcab479) Document metadata re-sync recovery steps - [`c340565`](https://github.com/RayLabsHQ/gitea-mirror/commit/c34056555f42c2ddae88e8fd9ec8923d01c1e1e4) Add bulk re-run metadata action ### 📊 Changes **4 files changed** (+234 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+14 -0) 📝 `src/components/repositories/Repository.tsx` (+91 -0) ➕ `src/pages/api/job/reset-metadata.ts` (+116 -0) ➕ `src/types/reset-metadata.ts` (+13 -0) </details> ### 📄 Description ## Summary - add a new bulk action in Repositories: **Re-run Metadata** - implement `POST /api/job/reset-metadata` to clear per-repo metadata state for selected repositories - after reset, immediately trigger Sync so metadata import runs again in one click - update README troubleshooting section with the UI-first recovery flow ## Why Addresses #170 with a simple UX path for recovering missed metadata after option changes, without adding complex runtime guards. ## Test - bun test --- <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-04-19 13:38:17 -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#1063
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?