Ooh, I didn’t know that someone had developed a mechanism to move issues and PRs.
I remember commenting on the fact that while it’s easy to move the source repo itself from location to location, as git makes that easy and self-contained, issues and PRs didn’t enjoy that.
I bet you could sync issues if you were bored enough. It’d be a pipeline that you have to maintain and two way syncs are a pain to maintain, but I bet it’s doable
Ooh, I didn’t know that someone had developed a mechanism to move issues and PRs.
I remember commenting on the fact that while it’s easy to move the source repo itself from location to location, as git makes that easy and self-contained, issues and PRs didn’t enjoy that.
You can easily do that with forgejo/gitea. However, you cannot sync these issues, that’s a one-off operation.
You can however totally sync the git repo - either out of the box or using web hooks/git hooks.
YMMV. I’ve seen issues in migration from Gitea to Codeberg. Always test first.
Ouch, and that is with Gitea and Codeberg being essentially the same software.
I bet you could sync issues if you were bored enough. It’d be a pipeline that you have to maintain and two way syncs are a pain to maintain, but I bet it’s doable