It seems like after a new repository has been created on GitHub, it will be automatically imported to Gitea Mirror, but not automatically mirrored.
Does this always require manually clicking the "mirror" Button, or can new repositories be mirrored automatically?
Originally created by @pschlo on GitHub (Apr 30, 2026).
Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/278
Originally assigned to: @arunavo4 on GitHub.
It seems like after a new repository has been created on GitHub, it will be automatically _imported_ to Gitea Mirror, but not automatically _mirrored_.
Does this always require manually clicking the "mirror" Button, or can new repositories be mirrored automatically?
Yes @pschlo currently needs manual. But I guess we can have it be automatically mirrored for people who want all of thier github to be mirrored and for people who want manual control there can be a checkbox or something they can uncheck.
<!-- gh-comment-id:4350196456 -->
@arunavo4 commented on GitHub (Apr 30, 2026):
Yes @pschlo currently needs manual. But I guess we can have it be automatically mirrored for people who want all of thier github to be mirrored and for people who want manual control there can be a checkbox or something they can uncheck.
Under "Configuration -> Connections -> GitHub Configuration -> Repository Selection" there is this option:
Auto-mirror new starred repositories.
When disabled, starred repos are imported for browsing but not automatically mirrored. You can still mirror individual repos manually.
Does this already do such automatic mirroring of newly starred repositories? Maybe this can be extended to also consider newly created own repositories.
However, the option currently does not seem to be working for me. A newly starred repository is auto-imported, but not mirrored, even though I have the option checked.
<!-- gh-comment-id:4351690516 -->
@pschlo commented on GitHub (Apr 30, 2026):
Under _"Configuration -> Connections -> GitHub Configuration -> Repository Selection"_ there is this option:
> **Auto-mirror new starred repositories.**
When disabled, starred repos are imported for browsing but not automatically mirrored. You can still mirror individual repos manually.
Does this already do such automatic mirroring of newly starred repositories? Maybe this can be extended to also consider newly created own repositories.
However, the option currently does not seem to be working for me. A newly starred repository is auto-imported, but **not** mirrored, even though I have the option checked.
The starred half of this is fixed in v3.15.8 — the "Auto-mirror new starred repositories" checkbox now works on its own. After upgrading, new stars should mirror on the next scheduled sync.
Leaving this open for the second half: surfacing auto-mirror for owned repos in the UI (it currently only works via the AUTO_MIRROR_REPOS=true env var).
<!-- gh-comment-id:4368045162 -->
@arunavo4 commented on GitHub (May 4, 2026):
The starred half of this is fixed in [v3.15.8](https://github.com/RayLabsHQ/gitea-mirror/releases/tag/v3.15.8) — the "Auto-mirror new starred repositories" checkbox now works on its own. After upgrading, new stars should mirror on the next scheduled sync.
Leaving this open for the second half: surfacing auto-mirror for *owned* repos in the UI (it currently only works via the `AUTO_MIRROR_REPOS=true` env var).
The owned-repo half is going up in #282 — adds a UI toggle for it under Configuration → Automation → Automatic Syncing so you no longer need to set AUTO_MIRROR_REPOS=true at container start.
Verified in dev: toggle persists across reload.
<!-- gh-comment-id:4368222855 -->
@arunavo4 commented on GitHub (May 4, 2026):
The owned-repo half is going up in #282 — adds a UI toggle for it under **Configuration → Automation → Automatic Syncing** so you no longer need to set `AUTO_MIRROR_REPOS=true` at container start.
Verified in dev: toggle persists across reload.
The owned half is shipped in v3.15.9 — toggle is at Configuration → Automation → Automatic Syncing. With this and the v3.15.8 starred fix, both halves of the original ask are covered. Closing once you confirm it works on your end.
<!-- gh-comment-id:4368306319 -->
@arunavo4 commented on GitHub (May 4, 2026):
The owned half is shipped in [v3.15.9](https://github.com/RayLabsHQ/gitea-mirror/releases/tag/v3.15.9) — toggle is at **Configuration → Automation → Automatic Syncing**. With this and the v3.15.8 starred fix, both halves of the original ask are covered. Closing once you confirm it works on your end.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @pschlo on GitHub (Apr 30, 2026).
Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/278
Originally assigned to: @arunavo4 on GitHub.
It seems like after a new repository has been created on GitHub, it will be automatically imported to Gitea Mirror, but not automatically mirrored.
Does this always require manually clicking the "mirror" Button, or can new repositories be mirrored automatically?
@arunavo4 commented on GitHub (Apr 30, 2026):
Yes @pschlo currently needs manual. But I guess we can have it be automatically mirrored for people who want all of thier github to be mirrored and for people who want manual control there can be a checkbox or something they can uncheck.
@pschlo commented on GitHub (Apr 30, 2026):
Under "Configuration -> Connections -> GitHub Configuration -> Repository Selection" there is this option:
Does this already do such automatic mirroring of newly starred repositories? Maybe this can be extended to also consider newly created own repositories.
However, the option currently does not seem to be working for me. A newly starred repository is auto-imported, but not mirrored, even though I have the option checked.
@arunavo4 commented on GitHub (May 4, 2026):
The starred half of this is fixed in v3.15.8 — the "Auto-mirror new starred repositories" checkbox now works on its own. After upgrading, new stars should mirror on the next scheduled sync.
Leaving this open for the second half: surfacing auto-mirror for owned repos in the UI (it currently only works via the
AUTO_MIRROR_REPOS=trueenv var).@arunavo4 commented on GitHub (May 4, 2026):
The owned-repo half is going up in #282 — adds a UI toggle for it under Configuration → Automation → Automatic Syncing so you no longer need to set
AUTO_MIRROR_REPOS=trueat container start.Verified in dev: toggle persists across reload.
@arunavo4 commented on GitHub (May 4, 2026):
The owned half is shipped in v3.15.9 — toggle is at Configuration → Automation → Automatic Syncing. With this and the v3.15.8 starred fix, both halves of the original ask are covered. Closing once you confirm it works on your end.
@arunavo4 commented on GitHub (May 19, 2026):
@pschlo Let me know if its working well for you.