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

[PR #181] [MERGED] Clarify mirror sync status and token-rotation troubleshooting #814

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

📋 Pull Request Information

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

Base: main ← Head: codex/issue-171-sync-reporting

📝 Commits (2)

  • fb60449 Clarify mirror sync status reporting
  • 888089b Merge branch 'main' into codex/issue-171-sync-reporting

📊 Changes

2 files changed (+11 additions, -3 deletions)

View changed files

📝 README.md (+8 -0)
📝 src/lib/gitea-enhanced.ts (+3 -3)

📄 Description

Summary

  • change sync activity wording from "Successfully synced" to "Sync requested" for mirror pull operations
  • clarify in details that Gitea/Forgejo performs pull-mirror updates asynchronously
  • add troubleshooting docs for GitHub token rotation on existing mirror repos

Why

Addresses #171 where backend logs can show pull-mirror auth failures even though sync request was accepted by Gitea/Forgejo.

🔄 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/181 **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-171-sync-reporting` --- ### 📝 Commits (2) - [`fb60449`](https://github.com/RayLabsHQ/gitea-mirror/commit/fb60449dc245b4f57f30026468297286ddd5a453) Clarify mirror sync status reporting - [`888089b`](https://github.com/RayLabsHQ/gitea-mirror/commit/888089b2d580471c98fd6d43b327d1c6e8773e7e) Merge branch 'main' into codex/issue-171-sync-reporting ### 📊 Changes **2 files changed** (+11 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+8 -0) 📝 `src/lib/gitea-enhanced.ts` (+3 -3) </details> ### 📄 Description ## Summary - change sync activity wording from "Successfully synced" to "Sync requested" for mirror pull operations - clarify in details that Gitea/Forgejo performs pull-mirror updates asynchronously - add troubleshooting docs for GitHub token rotation on existing mirror repos ## Why Addresses #171 where backend logs can show pull-mirror auth failures even though sync request was accepted by Gitea/Forgejo. --- <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:47 -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#814
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?