I haven't looked at the status of how issues are handled, but my two main priorities are being able to mirror packages and releases. Does this script take care of these?
Gitea has a PR open to develop an "all-in-one" mirror utility, but it hasn't been finished yet, and it looks like it has been pushed back to the next major release.
My biggest issues with Gitea mirroring is:
1. Releases
2. Packages
3. Issues
I haven't looked at the status of how issues are handled, but my two main priorities are being able to mirror packages and releases. Does this script take care of these?
Gitea has a PR open to develop an "all-in-one" mirror utility, but it hasn't been finished yet, and it looks like it has been pushed back to the next major release.
<!-- github-sync-id:3147007606 -->
Are there possibly plans to migrate packages in the future? That's a huge pain about Gitea, and whenever I build an image on Github, I have to generate a workflow just for gitea,.
Missed this.
Are there possibly plans to migrate packages in the future? That's a huge pain about Gitea, and whenever I build an image on Github, I have to generate a workflow just for gitea,.
<!-- github-comment-id:2981475815 -->
I see, will keep this issue Open then. I have done some initial research it it possible to do this so will have to see if i get the time to integrate this.
I see, will keep this issue Open then. I have done some initial research it it possible to do this so will have to see if i get the time to integrate this.
<!-- github-comment-id:2982433660 -->
Having package integration would be friggen amazing.
I'm using Gickup right now, which doesn't offer release syncing, so I wanted to migrate over to gitea-mirror, but I wanted to confirm first and see where the project was at.
Having package integration would be friggen amazing.
I'm using Gickup right now, which doesn't offer release syncing, so I wanted to migrate over to gitea-mirror, but I wanted to confirm first and see where the project was at.
<!-- github-comment-id:2982568304 -->
Releases with their assets and issues are both mirrored, you can switch them on under the mirror options. Packages are out of scope: GitHub packages span several registries (npm, containers, Maven and so on), each with its own protocol, and there is no generic way to move them into Gitea's registry. Marking this as won't do.
Releases with their assets and issues are both mirrored, you can switch them on under the mirror options. Packages are out of scope: GitHub packages span several registries (npm, containers, Maven and so on), each with its own protocol, and there is no generic way to move them into Gitea's registry. Marking this as won't do.
<!-- github-comment-id:5506864844 -->
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.
My biggest issues with Gitea mirroring is:
I haven't looked at the status of how issues are handled, but my two main priorities are being able to mirror packages and releases. Does this script take care of these?
Gitea has a PR open to develop an "all-in-one" mirror utility, but it hasn't been finished yet, and it looks like it has been pushed back to the next major release.
Hi @aetherinox Releases and Issues is mirrored but the packages are not.
Missed this.
Are there possibly plans to migrate packages in the future? That's a huge pain about Gitea, and whenever I build an image on Github, I have to generate a workflow just for gitea,.
I see, will keep this issue Open then. I have done some initial research it it possible to do this so will have to see if i get the time to integrate this.
Having package integration would be friggen amazing.
I'm using Gickup right now, which doesn't offer release syncing, so I wanted to migrate over to gitea-mirror, but I wanted to confirm first and see where the project was at.
Will update on this issue when this lands
Releases with their assets and issues are both mirrored, you can switch them on under the mirror options. Packages are out of scope: GitHub packages span several registries (npm, containers, Maven and so on), each with its own protocol, and there is no generic way to move them into Gitea's registry. Marking this as won't do.