this post was submitted on 30 Mar 2025
734 points (99.1% liked)

Selfhosted

45341 readers
666 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
734
Organic Maps migrates to Forgejo due to GitHub account blocked by Microsoft. (programming.dev)
submitted 2 days ago by vegetaaaaaaa@lemmy.world to c/selfhosted@lemmy.world
41 comments fedilink hide all child comments
 

cross-posted from: https://feddit.org/post/9959466

geteilt von: https://programming.dev/post/27692275

you are viewing a single comment's thread
view the rest of the comments
[–] tal 21 points 2 days ago* (last edited 2 days ago) (1 children)

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.

[–] marsokod@lemmy.world 18 points 2 days ago (2 children)

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.

[–] IcyToes@sh.itjust.works 5 points 2 days ago (1 children)

YMMV. I've seen issues in migration from Gitea to Codeberg. Always test first.

[–] marsokod@lemmy.world 1 points 1 day ago

Ouch, and that is with Gitea and Codeberg being essentially the same software.

[–] Chocrates@lemmy.world 3 points 2 days ago

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