[GH-ISSUE #131] Create a matrix of Source <-> Target Git repo Mirroring #66

New issue

Open

opened 2026-02-27 15:54:54 +03:00 by kerem · 3 comments

kerem commented

2026-02-27 15:54:54 +03:00

Owner

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

It would be helpful if you could configure multiple git servers, and the mirroring action of each.
So something like this:

Source	Target	Source Instance	Target Instance	Mirror Type
Github	Gitea	https://github.com	https://my-gitea-instance.internal	=> (Source to Target)
Github	Gitlab	https://github.com	https://gitlab.com	<=> (Two Way Mirror)
Gitea	Gitea	https://my-gitea-instance.internal	https://localhost:3000	=> (Source to Target)
Gitlab	Gitea	https:gitlab.com	https://localhost:3000	=> (Source to Target)

This would be helpful as there are many git servers (public, company, self hosted, internal), and people may want to have repos mirrored in certain ways depending on the source and target servers.

This would also solve issues:
#16
#26
#34 .

This would allow greater flexibility of how repos are mirrored, which is goof for people not just wanting github->gitea mirroring.

Originally created by @micah686 on GitHub (Oct 24, 2025). Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/131 It would be helpful if you could configure multiple git servers, and the mirroring action of each. So something like this: | Source | Target | Source Instance | Target Instance | Mirror Type | |--------|--------|------------------------------------|------------------------------------|-----------------------| | Github | Gitea | https://github.com | https://my-gitea-instance.internal | => (Source to Target) | | Github | Gitlab | https://github.com | https://gitlab.com | <=> (Two Way Mirror) | | Gitea | Gitea | https://my-gitea-instance.internal | https://localhost:3000 | => (Source to Target) | | Gitlab | Gitea | https:gitlab.com | https://localhost:3000 | => (Source to Target) | This would be helpful as there are many git servers (public, company, self hosted, internal), and people may want to have repos mirrored in certain ways depending on the source and target servers. This would also solve issues: #16 #26 #34 . This would allow greater flexibility of how repos are mirrored, which is goof for people not just wanting github->gitea mirroring.

kerem added the

enhancement

help wanted

labels

2026-02-27 15:54:54 +03:00

kerem commented

2026-02-27 15:54:55 +03:00

Author

Owner

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

Hi @micah686 I understand this requirement but this would required a significant amount of time building and testing each of them and since this is a free and open source project with no sponsorship I am currently blocked for next few months. I am happy to add community tested PR's on this. And I can also help out reviewing and testing things on the weekends.
And personally I built this cause I just wanted a backup of my GitHub repos so adding these features don't really serve any personal reason. Hence I think a community PR on these issues would be the right call. I can help with reviewing and testing them on my free weekends.

@arunavo4 commented on GitHub (Oct 25, 2025): Hi @micah686 I understand this requirement but this would required a significant amount of time building and testing each of them and since this is a free and open source project with no sponsorship I am currently blocked for next few months. I am happy to add community tested PR's on this. And I can also help out reviewing and testing things on the weekends. And personally I built this cause I just wanted a backup of my GitHub repos so adding these features don't really serve any personal reason. Hence I think a community PR on these issues would be the right call. I can help with reviewing and testing them on my free weekends.

kerem commented

2026-02-27 15:54:55 +03:00

Author

Owner

@micah686 commented on GitHub (Oct 25, 2025):

Yeah, I understand your position. I just thought this would be a good feature to work toward (long term wise).
I had written a simple C# console app to do something similar to what you did, but your solution is a lot more in depth than mine ever was.
If I could help out, I would, but I don't know typescript well enough.
I just noticed there were other issues asking for mirroring from/to different git servers, and I figured it would be better to slowly work on a solution that's expandable for mirroring to/from different git servers.

The project looks really nice so far, and I'm interested to see how it improves.

@micah686 commented on GitHub (Oct 25, 2025): Yeah, I understand your position. I just thought this would be a good feature to work toward (long term wise). I had written a simple C# console app to do something similar to what you did, but your solution is a lot more in depth than mine ever was. If I could help out, I would, but I don't know typescript well enough. I just noticed there were other issues asking for mirroring from/to different git servers, and I figured it would be better to slowly work on a solution that's expandable for mirroring to/from different git servers. The project looks really nice so far, and I'm interested to see how it improves.

kerem commented

2026-02-27 15:54:55 +03:00

Author

Owner

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

@micah686 Yea I think long term wise I def see that this can be a good roadmap and overtime with enough interest from community and using my weekends maybe we will get there with all these options sometime next year.

@arunavo4 commented on GitHub (Oct 25, 2025): @micah686 Yea I think long term wise I def see that this can be a good roadmap and overtime with enough interest from community and using my weekends maybe we will get there with all these options sometime next year.

kerem referenced this issue

2026-02-27 15:55:12 +03:00

[PR #66] [MERGED] 🔥 Added shader hero component #116