github-starred/gitea-mirror
2
0
Fork 0
mirror of https://github.com/RayLabsHQ/gitea-mirror.git synced 2026-05-08 20:58:16 -05:00
Code Issues 103 Packages Projects Releases 97 Wiki Activity

[PR #184] [MERGED] Implement incremental issue and PR metadata sync #817

New Issue
Closed
opened 2026-04-16 02:46:55 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-16 02:46:55 -05:00
Owner
Copy Link

📋 Pull Request Information

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

Base: main ← Head: codex/issue-165-incremental-metadata

📝 Commits (2)

  • 85b1867 Implement incremental issue and PR metadata sync
  • cb7510f Improve legacy matching and comment dedupe

📊 Changes

3 files changed (+270 additions, -118 deletions)

View changed files

📝 src/lib/gitea-enhanced.test.ts (+3 -3)
📝 src/lib/gitea-enhanced.ts (+2 -18)
📝 src/lib/gitea.ts (+265 -97)

📄 Description

Summary

  • remove the skip-forever gate for issues/PR metadata on sync
  • make issue mirroring idempotent by upserting based on GitHub issue number markers
  • backfill legacy issue entries by one-time title matching when possible
  • prevent duplicate mirrored comments using a hidden gh-comment-id marker
  • make PR mirroring idempotent by updating existing [PR #N] entries instead of recreating
  • update tests to assert incremental re-sync behavior

Why

Fixes the behavior in #165 where issue/PR metadata stopped updating after the first sync.

Validation

  • bun test src/lib/gitea-enhanced.test.ts
  • bun test src/lib/gitea.test.ts src/lib/mirror-sync-fix.test.ts
  • bun run build

Fixes #165

🔄 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/184 **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-165-incremental-metadata` --- ### 📝 Commits (2) - [`85b1867`](https://github.com/RayLabsHQ/gitea-mirror/commit/85b1867490f7b82b62cf32db519b0cac65728cb2) Implement incremental issue and PR metadata sync - [`cb7510f`](https://github.com/RayLabsHQ/gitea-mirror/commit/cb7510f79ddc8422cc1a2375180adb7a8655934b) Improve legacy matching and comment dedupe ### 📊 Changes **3 files changed** (+270 additions, -118 deletions) <details> <summary>View changed files</summary> 📝 `src/lib/gitea-enhanced.test.ts` (+3 -3) 📝 `src/lib/gitea-enhanced.ts` (+2 -18) 📝 `src/lib/gitea.ts` (+265 -97) </details> ### 📄 Description ## Summary - remove the skip-forever gate for issues/PR metadata on sync - make issue mirroring idempotent by upserting based on GitHub issue number markers - backfill legacy issue entries by one-time title matching when possible - prevent duplicate mirrored comments using a hidden `gh-comment-id` marker - make PR mirroring idempotent by updating existing `[PR #N]` entries instead of recreating - update tests to assert incremental re-sync behavior ## Why Fixes the behavior in #165 where issue/PR metadata stopped updating after the first sync. ## Validation - `bun test src/lib/gitea-enhanced.test.ts` - `bun test src/lib/gitea.test.ts src/lib/mirror-sync-fix.test.ts` - `bun run build` Fixes #165 --- <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-16 02:46:55 -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#817
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?