@vegetaaaaaaa@lemmy.world to Selfhosted@lemmy.worldEnglish • 4 days agoOrganic Maps migrates to Forgejo due to GitHub account blocked by Microsoft.programming.devimagemessage-square41fedilinkarrow-up1752arrow-down17file-text
arrow-up1745arrow-down1imageOrganic Maps migrates to Forgejo due to GitHub account blocked by Microsoft.programming.dev@vegetaaaaaaa@lemmy.world to Selfhosted@lemmy.worldEnglish • 4 days agomessage-square41fedilinkfile-text
cross-posted from: https://feddit.org/post/9959466 geteilt von: https://programming.dev/post/27692275 Post New Git Repo.
minus-squaremarsokodlinkfedilinkEnglish18•4 days agoYou 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.
minus-square@IcyToes@sh.itjust.workslinkfedilinkEnglish5•4 days agoYMMV. I’ve seen issues in migration from Gitea to Codeberg. Always test first.
minus-squaremarsokodlinkfedilinkEnglish2•3 days agoOuch, and that is with Gitea and Codeberg being essentially the same software.
minus-squareChrislinkfedilinkEnglish3•4 days agoI 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
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