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

[GH-ISSUE #133] Issues are not sync's/updated if not configured during initial mirror. #929

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

Originally created by @mayankchetan on GitHub (Oct 25, 2025).
Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/133

Originally assigned to: @arunavo4 on GitHub.

Noticed that if a previously mirrored repository is "synced" after modifying configuration (eg: to sync repository meta data), the issues and PR's are not sync's/updated.

This is NOT an issue if the repositories are mirrored after modifying the configuration.

Steps:

  1. Start a new gitea-mirror and 'gitea' instances.
  2. Configure settings WITHOUT selecting Releases & Tags and Repository Metadata under Content & Data.
  3. Add a repository and mirror it. Notice Releases and issues ( & PR) are not sync'd.
  4. Go to configurations and select Releases & Tags and Repository Metadata under Content & Data.
  5. sync the repository.
  6. Only Releases are sync'd but not issues & PR

Happy to share additional details/screenshots if needed.

Thanks,
Mayank

Originally created by @mayankchetan on GitHub (Oct 25, 2025). Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/133 Originally assigned to: @arunavo4 on GitHub. Noticed that if a previously mirrored repository is "synced" after modifying configuration (eg: to sync repository meta data), the issues and PR's are not sync's/updated. This is NOT an issue if the repositories are mirrored after modifying the configuration. Steps: 1. Start a new `gitea-mirror` and 'gitea' instances. 2. Configure settings WITHOUT selecting `Releases & Tags` and `Repository Metadata` under `Content & Data`. 3. Add a repository and mirror it. Notice `Releases` and `issues ( & PR)` are not sync'd. 4. Go to configurations and select `Releases & Tags` and `Repository Metadata` under `Content & Data`. 5. `sync` the repository. 6. Only `Releases` are sync'd but not `issues & PR` Happy to share additional details/screenshots if needed. Thanks, Mayank
GiteaMirror added the enhancement label 2026-04-19 13:32:17 -05:00
GiteaMirror commented 2026-04-19 13:32:19 -05:00
Author
Owner
Copy Link

@arunavo4 commented on GitHub (Oct 26, 2025):

@mayankchetan give this PR image a try ghcr.io/raylabshq/gitea-mirror:pr-136

<!-- gh-comment-id:3447981880 --> @arunavo4 commented on GitHub (Oct 26, 2025): @mayankchetan give this PR image a try `ghcr.io/raylabshq/gitea-mirror:pr-136`
GiteaMirror commented 2026-04-19 13:32:21 -05:00
Author
Owner
Copy Link

@mayankchetan commented on GitHub (Oct 26, 2025):

Thanks again @arunavo4, works prefectly!

<!-- gh-comment-id:3449025286 --> @mayankchetan commented on GitHub (Oct 26, 2025): Thanks again @arunavo4, works prefectly!
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 enhancement
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#929
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?