github-starred/gitea-mirror
2
0
Fork 0
mirror of https://github.com/RayLabsHQ/gitea-mirror.git synced 2026-05-22 07:31:36 -05:00
Code Issues 140 Packages Projects Releases 100 Wiki Activity

[GH-ISSUE #205] Feature Request: Granular Control Over Metadata Sync for Starred Repositories #1710

New Issue
Closed
opened 2026-04-27 19:03:08 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-04-27 19:03:08 -05:00
Owner
Copy Link

Originally created by @kapdon on GitHub (Mar 2, 2026).
Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/205

Originally assigned to: @arunavo4 on GitHub.

First of all, I set this up last night — amazing piece of software. Really impressed with how smooth the experience is.

I have a couple of questions / feature requests:

Granular metadata control:
Is there a way to control, at a more granular level, which repositories receive which metadata? For example, being able to configure metadata rules per repository (or per group of repositories) rather than applying the same behavior globally.

Selective sync for starred repositories:
Is it possible to import starred repositories but choose which ones should actually be synced?

Last night, it attempted to mirror and sync all ~800 of my starred repositories lol. I originally assumed it would only sync the ones I had manually mirrored, so this caught me by surprise.

It would be great to have an option to where the default isn't mirror and sync all but only sync those that have been manually mirrored.

Originally created by @kapdon on GitHub (Mar 2, 2026). Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/205 Originally assigned to: @arunavo4 on GitHub. First of all, I set this up last night — amazing piece of software. Really impressed with how smooth the experience is. I have a couple of questions / feature requests: **Granular metadata control:** Is there a way to control, at a more granular level, which repositories receive which metadata? For example, being able to configure metadata rules per repository (or per group of repositories) rather than applying the same behavior globally. **Selective sync for starred repositories:** Is it possible to import starred repositories but choose which ones should actually be synced? Last night, it attempted to mirror and sync all ~800 of my starred repositories lol. I originally assumed it would only sync the ones I had manually mirrored, so this caught me by surprise. It would be great to have an option to where the default isn't `mirror and sync all` but only sync those that have been manually mirrored.
GiteaMirror added the questionenhancement labels 2026-04-27 19:03:08 -05:00
GiteaMirror commented 2026-04-27 19:03:19 -05:00
Author
Owner
Copy Link

@arunavo4 commented on GitHub (Mar 2, 2026):

@kapdon there is a button next to each repo in the table where you can mirror and sync only that. also you can stop syncing any particular repo.

<!-- gh-comment-id:3982059696 --> @arunavo4 commented on GitHub (Mar 2, 2026): @kapdon there is a button next to each repo in the table where you can mirror and sync only that. also you can stop syncing any particular repo.
GiteaMirror commented 2026-04-27 19:03:23 -05:00
Author
Owner
Copy Link

@kapdon commented on GitHub (Mar 2, 2026):

@kapdon there is a button next to each repo in the table where you can mirror and sync only that. also you can stop syncing any particular repo.

  • Enable “Sync Starred Repositories” so that starred repositories are pulled into the table.
    • Note: If you do not enable this, “Import GitHub Data” only imports your own repositories, so there's no way to manually select repo to sync.
  • Select all and ignore all repositories
  • Manually enable, and mirror the one you want.

it kinda works, have to disable or enable new repos as you star more repos in github.
alternatively if you do the following:

  • Manually enable, and mirror the one you want.
  • Disable “Sync Starred Repositories.”
  • Wait for the scheduled “Sync every hour” job to trigger.
  • it triggers but never syncs the repo you manually mirrored.

also if you reboot the compose stack while you just have imported github data and haven't done anything else it'll start mirroring all the repository upon restart immediately.

<!-- gh-comment-id:3983976745 --> @kapdon commented on GitHub (Mar 2, 2026): > [@kapdon](https://github.com/kapdon) there is a button next to each repo in the table where you can mirror and sync only that. also you can stop syncing any particular repo. - Enable “Sync Starred Repositories” so that starred repositories are pulled into the table. - Note: If you do not enable this, “Import GitHub Data” only imports your own repositories, so there's no way to manually select repo to sync. - Select all and ignore all repositories - Manually enable, and mirror the one you want. it kinda works, have to disable or enable new repos as you star more repos in github. alternatively if you do the following: - Manually enable, and mirror the one you want. - Disable “Sync Starred Repositories.” - Wait for the scheduled “Sync every hour” job to trigger. - it triggers but never syncs the repo you manually mirrored. also if you reboot the compose stack while you just have imported github data and haven't done anything else it'll start mirroring all the repository upon restart immediately.
GiteaMirror commented 2026-04-27 19:03:28 -05:00
Author
Owner
Copy Link

@kapdon commented on GitHub (Mar 3, 2026):

testing #208

  • import github + starred repo, uncheck auto-sync, reboot compose stack, no sync ✅
  • disable sync starred repo, reboot compose, existing sync's repo did not get archived ✅
  • leaving sync starred repo unchecked, waiting for an hour right now to see if automated sync will continue to sync existing mirrored repo regardless if it's starred or not, it does ✅

oh also unrelated thing I starred a new repo after the inital import, it was picked up properly as dashboard repository section shows this new repo has been imported, but the activity log has no such record of it being imported even after refreshing

<!-- gh-comment-id:3994273294 --> @kapdon commented on GitHub (Mar 3, 2026): testing #208 - import github + starred repo, uncheck `auto-sync`, reboot compose stack, no sync ✅ - disable sync starred repo, reboot compose, existing sync's repo did not get archived ✅ - leaving sync starred repo unchecked, waiting for an hour right now to see if automated sync will continue to sync existing mirrored repo regardless if it's starred or not, it does ✅ oh also unrelated thing I starred a new repo after the inital import, it was picked up properly as dashboard repository section shows this new repo has been imported, but the activity log has no such record of it being imported even after refreshing
GiteaMirror commented 2026-04-27 19:03:29 -05:00
Author
Owner
Copy Link

@arunavo4 commented on GitHub (Mar 4, 2026):

@kapdon Thanks a lot for testing it. Let me see why the event was missed.

<!-- gh-comment-id:3994875197 --> @arunavo4 commented on GitHub (Mar 4, 2026): @kapdon Thanks a lot for testing it. Let me see why the event was missed.
GiteaMirror commented 2026-04-27 19:03:31 -05:00
Author
Owner
Copy Link

@arunavo4 commented on GitHub (Mar 4, 2026):

@kapdon That new issue should be fixed now.

<!-- gh-comment-id:3994910788 --> @arunavo4 commented on GitHub (Mar 4, 2026): @kapdon That new issue should be fixed now.
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 question
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#1710
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?