cross-posted from: https://feddit.org/post/9959466
geteilt von: https://programming.dev/post/27692275
this post was submitted on 30 Mar 2025
772 points (99.1% liked)
Selfhosted
59999 readers
421 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam.
-
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
-
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
-
Submission headline should match the article title.
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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