Hey Jonas! I was analyzing different approaches for mirroring GitHub repositories to Gitea and came across your repository. I really liked your solution for syncing issues and metadata over time.
I was building my own setup and decided to take a slightly different approach: I wrote a Python script that leverages Gitea's native /api/v1/repos/migrate API to do a one-time 1:1 metadata migration (issues, wikis, releases) and also automatically recreates GitHub organization structures on the Gitea side before migrating.
It might not have your continuous manual issue-sync engine, but it's a solid alternative for people doing initial bulk migrations who want native organization preservation. Just wanted to share it here in case anyone looking through the issues finds it useful:
https://github.com/yuanweize/gitea-github-mirror
Thanks for open-sourcing your code, analyzing your manual metadata syncing logic was really insightful!
Hey Jonas! I was analyzing different approaches for mirroring GitHub repositories to Gitea and came across your repository. I really liked your solution for syncing issues and metadata over time.
I was building my own setup and decided to take a slightly different approach: I wrote a Python script that leverages Gitea's native
/api/v1/repos/migrateAPI to do a one-time 1:1 metadata migration (issues, wikis, releases) and also automatically recreates GitHub organization structures on the Gitea side before migrating.It might not have your continuous manual issue-sync engine, but it's a solid alternative for people doing initial bulk migrations who want native organization preservation. Just wanted to share it here in case anyone looking through the issues finds it useful:
https://github.com/yuanweize/gitea-github-mirror
Thanks for open-sourcing your code, analyzing your manual metadata syncing logic was really insightful!