Mirror Summary #6827

New Issue

GiteaMirror · 2025-11-02T07:07:41-06:00

GiteaMirror commented

2025-11-02 07:07:41 -06:00

Originally created by @lunny on GitHub (Feb 8, 2021).

~~Mirror issues along with the repo #1876~~
Mirror new-created wiki when repositories migrated #2309
Reverse mirroring, from Gitea to remote Github/Gitlab/Gitea and etc. #3480
Mirror repositories could not be readonly and Allow to push commits manually #7609
Mirror an entire github organization into gitea organization #8424
Mirror Topics Support automatic fetching of new content when an issue has new comments (#14590)
Mirror Docs

Originally created by @lunny on GitHub (Feb 8, 2021). * [x] ~~Mirror issues along with the repo #1876~~ * [ ] Mirror new-created wiki when repositories migrated #2309 * [x] Reverse mirroring, from Gitea to remote Github/Gitlab/Gitea and etc. #3480 * [ ] Mirror repositories could not be readonly and Allow to push commits manually #7609 * [ ] Mirror an entire github organization into gitea organization #8424 * [ ] Mirror Topics #14590 * [ ] Mirror Docs

GiteaMirror added the type/summary label 2025-11-02 07:07:41 -06:00

GiteaMirror commented

2025-11-02 07:07:42 -06:00

@c4lliope commented on GitHub (Feb 8, 2021):

I searched for "Mirror" on https://docs.gitea.io, and I didn't see much describing how mirrors run;
e.g. what happens automatically (git pull, git prune from the origin codebase?)
and what must be updated by a manual process (issues, wiki pages).

Someone visiting gitea.com as an end user will probably need a summary page
of the purpose and mechanisms of mirror repositories.
Maybe a paragraph on the "import repository" page could help people learn more.

@c4lliope commented on GitHub (Feb 8, 2021): I searched for "Mirror" on https://docs.gitea.io, and I didn't see much describing how mirrors run; e.g. what happens automatically (`git pull`, `git prune` from the origin codebase?) and what must be updated by a manual process (issues, wiki pages). Someone visiting `gitea.com` as an end user will probably need a summary page of the purpose and mechanisms of mirror repositories. Maybe a paragraph on the "import repository" page could help people learn more.

GiteaMirror commented

2025-11-02 07:07:42 -06:00

@kdumontnu commented on GitHub (Feb 8, 2021):

Is https://github.com/go-gitea/gitea/issues/3480 a duplicate issue to https://github.com/go-gitea/gitea/issues/7609?

@kdumontnu commented on GitHub (Feb 8, 2021): Is https://github.com/go-gitea/gitea/issues/3480 a duplicate issue to https://github.com/go-gitea/gitea/issues/7609?

GiteaMirror commented

2025-11-02 07:07:42 -06:00

@lunny commented on GitHub (Feb 9, 2021):

@kdumontnu I think it's not the same. #3480 means a reverse mirror, #7609 means a mirror repository could be not readonly.

@lunny commented on GitHub (Feb 9, 2021): @kdumontnu I think it's not the same. #3480 means a reverse mirror, #7609 means a mirror repository could be not readonly.

GiteaMirror commented

2025-11-02 07:07:43 -06:00

@lunny commented on GitHub (Feb 9, 2021):

I searched for "Mirror" on https://docs.gitea.io, and I didn't see much describing how mirrors run;
e.g. what happens automatically (git pull, git prune from the origin codebase?)
and what must be updated by a manual process (issues, wiki pages).

Someone visiting gitea.com as an end user will probably need a summary page
of the purpose and mechanisms of mirror repositories.
Maybe a paragraph on the "import repository" page could help people learn more.

Yes, mirror docs is also needed.

@lunny commented on GitHub (Feb 9, 2021): > I searched for "Mirror" on https://docs.gitea.io, and I didn't see much describing how mirrors run; > e.g. what happens automatically (`git pull`, `git prune` from the origin codebase?) > and what must be updated by a manual process (issues, wiki pages). > > Someone visiting `gitea.com` as an end user will probably need a summary page > of the purpose and mechanisms of mirror repositories. > Maybe a paragraph on the "import repository" page could help people learn more. Yes, mirror docs is also needed.

GiteaMirror commented

2025-11-02 07:07:43 -06:00

@kdumontnu commented on GitHub (Feb 9, 2021):

@lunny thx, but the syntax is very confusing then. You say "Reverse mirroring #7609" above, but "#3480 means reverse mirror".

Do you mean then: "Enable pushing to Gitea repo configured as secondary mirror #7609"?
And "Enable Gitea as primary in mirror configuration #3480"?

We can use consistent diction for mirrors as "primary (push)" and "secondary (pull)"

Also, I added a bounty to #3480 if you can add the following:

[![Bountysource](https://api.bountysource.com/badge/issue?issue_id=54827645)](https://www.bountysource.com/issues/54827645-ability-to-automatically-push-to-remote-mirror-repository)

Enable Gitea as primary in mirror configuration #3480

@kdumontnu commented on GitHub (Feb 9, 2021): @lunny thx, but the syntax is very confusing then. You say "Reverse mirroring #7609" above, but "#3480 means reverse mirror". Do you mean then: "Enable pushing to Gitea repo configured as secondary mirror #7609"? And "Enable Gitea as primary in mirror configuration #3480"? We can use consistent diction for mirrors as "primary (push)" and "secondary (pull)" --- Also, I added a bounty to #3480 if you can add the following: ``` [![Bountysource](https://api.bountysource.com/badge/issue?issue_id=54827645)](https://www.bountysource.com/issues/54827645-ability-to-automatically-push-to-remote-mirror-repository) ``` - Enable Gitea as primary in mirror configuration #3480 [![Bountysource](https://api.bountysource.com/badge/issue?issue_id=54827645)](https://www.bountysource.com/issues/54827645-ability-to-automatically-push-to-remote-mirror-repository)

GiteaMirror commented

2025-11-02 07:07:43 -06:00

@lunny commented on GitHub (Feb 9, 2021):

@lunny thx, but the syntax is very confusing then. You say "Reverse mirroring #7609" above, but "#3480 means reverse mirror".

Do you mean then: "Enable pushing to Gitea repo configured as secondary mirror #7609"?
And "Enable Gitea as primary in mirror configuration #3480"?

We can use consistent diction for mirrors as "primary (push)" and "secondary (pull)"

Also, I added a bounty to #3480 if you can add the following:
[![Bountysource](https://api.bountysource.com/badge/issue?issue_id=54827645)](https://www.bountysource.com/issues/54827645-ability-to-automatically-push-to-remote-mirror-repository)
Enable Gitea as primary in mirror configuration #3480

Thanks, I have updated the issue content. I haven't followed your advise because I think primary and secondary is still confusing. Please let me know if you think it's still confusing. :)

@lunny commented on GitHub (Feb 9, 2021): > @lunny thx, but the syntax is very confusing then. You say "Reverse mirroring #7609" above, but "#3480 means reverse mirror". > > Do you mean then: "Enable pushing to Gitea repo configured as secondary mirror #7609"? > And "Enable Gitea as primary in mirror configuration #3480"? > > We can use consistent diction for mirrors as "primary (push)" and "secondary (pull)" > > Also, I added a bounty to #3480 if you can add the following: > > ``` > [![Bountysource](https://api.bountysource.com/badge/issue?issue_id=54827645)](https://www.bountysource.com/issues/54827645-ability-to-automatically-push-to-remote-mirror-repository) > ``` > > * Enable Gitea as primary in mirror configuration #3480 [![Bountysource](https://camo.githubusercontent.com/201b3d010d481c895733bcec38918445b78cbdd27c8a720ead1e80ba63029d22/68747470733a2f2f6170692e626f756e7479736f757263652e636f6d2f62616467652f69737375653f69737375655f69643d3534383237363435)](https://www.bountysource.com/issues/54827645-ability-to-automatically-push-to-remote-mirror-repository) Thanks, I have updated the issue content. I haven't followed your advise because I think `primary` and `secondary` is still confusing. Please let me know if you think it's still confusing. :)

GiteaMirror commented

2025-11-02 07:07:44 -06:00

@6543 commented on GitHub (May 17, 2021):

Option to "protect" mirrors (dont sync if it will drop commits or is a completly new history)

@6543 commented on GitHub (May 17, 2021): Option to "protect" mirrors (dont sync if it will drop commits or is a completly new history)

GiteaMirror commented

2025-11-02 07:07:44 -06:00

@a1012112796 commented on GitHub (May 22, 2021):

suggest add https://gitee.com support, from #15945

@a1012112796 commented on GitHub (May 22, 2021): suggest add https://gitee.com support, from #15945

GiteaMirror commented

2025-11-02 07:07:44 -06:00

@6543 commented on GitHub (May 22, 2021):

@a1012112796 wrong summary issue :)

Do you mean #8689?

@6543 commented on GitHub (May 22, 2021): @a1012112796 wrong summary issue :) Do you mean #8689?

GiteaMirror commented

2025-11-02 07:07:45 -06:00

@Sirttas commented on GitHub (Aug 16, 2021):

I would suggest in addition to the issue #3480 to add the ability to only push certain branch, tags, etc.

@Sirttas commented on GitHub (Aug 16, 2021): I would suggest in addition to the issue #3480 to add the ability to only push certain branch, tags, etc.

GiteaMirror commented

2025-11-02 07:07:45 -06:00

@culmat commented on GitHub (Jan 9, 2022):