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

[GH-ISSUE #170] How to retry missed content #1702

New Issue
Closed
opened 2026-04-27 19:01:37 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-27 19:01:37 -05:00
Owner
Copy Link

Originally created by @Bluscream on GitHub (Jan 21, 2026).
Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/170

Since the container doesnt allow setting these

directly via ENV vars, i have to set them manually after ccontainer startup, that means there are some repos now where these content items have been missed syncing. Is there a way to tell the app to re-sync every single repo to fetch missing items and sync them?

Originally created by @Bluscream on GitHub (Jan 21, 2026). Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/170 Since the container doesnt allow setting these ![](https://files.catbox.moe/oplbrs.png) directly via ENV vars, i have to set them manually after ccontainer startup, that means there are some repos now where these content items have been missed syncing. Is there a way to tell the app to re-sync every single repo to fetch missing items and sync them?
GiteaMirror commented 2026-04-27 19:01:42 -05:00
Author
Owner
Copy Link

@arunavo4 commented on GitHub (Feb 24, 2026):

Yes. Today the simplest recovery path is:

  1. Enable the metadata options you want in Configuration.
  2. Go to Repositories, select affected repos, and click Sync.
  3. If some repos still miss metadata, clear metadata sync state and sync again:
sqlite3 data/gitea-mirror.db "UPDATE repositories SET metadata = NULL;"

That resets per-repo metadata completion flags so metadata steps run again on next sync.

I also opened a docs PR so this flow is captured in README: #180.

<!-- gh-comment-id:3948908033 --> @arunavo4 commented on GitHub (Feb 24, 2026): Yes. Today the simplest recovery path is: 1. Enable the metadata options you want in Configuration. 2. Go to Repositories, select affected repos, and click **Sync**. 3. If some repos still miss metadata, clear metadata sync state and sync again: ```bash sqlite3 data/gitea-mirror.db "UPDATE repositories SET metadata = NULL;" ``` That resets per-repo metadata completion flags so metadata steps run again on next sync. I also opened a docs PR so this flow is captured in README: #180.
GiteaMirror commented 2026-04-27 19:01:47 -05:00
Author
Owner
Copy Link

@arunavo4 commented on GitHub (Feb 24, 2026):

Implemented in #180: there is now a Re-run Metadata bulk button in Repositories. It clears metadata state for selected repos and starts Sync immediately (one click, no DB command needed).

<!-- gh-comment-id:3948918134 --> @arunavo4 commented on GitHub (Feb 24, 2026): Implemented in #180: there is now a **Re-run Metadata** bulk button in Repositories. It clears metadata state for selected repos and starts Sync immediately (one click, no DB command needed).
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
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#1702
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?