this post was submitted on 02 Dec 2025
25 points (93.1% liked)

Git

4027 readers
1 users here now

Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.

Resources

Rules

  1. Follow programming.dev rules
  2. Be excellent to each other, no hostility towards users for any reason
  3. No spam of tools/companies/advertisements. It’s OK to post your own stuff part of the time, but the primary use of the community should not be self-promotion.

Git Logo by Jason Long is licensed under the Creative Commons Attribution 3.0 Unported License.

founded 2 years ago
MODERATORS
Ategon@programming.dev
canpolat@programming.dev
jnovinger@programming.dev
25
Getting out of "evil" GitHub (sh.itjust.works)
submitted 2 weeks ago* (last edited 2 weeks ago) by dogs0n@sh.itjust.works to c/git@programming.dev
6 comments fedilink hide all child comments
 

Just to be clear: I'm not asking for github alternatives.

If you had an open source project that is somewhat deeply rooted in GitHub's ecosystem and wanted to move to another service, how would you proceed?

I'd really want to self host a service, but then i'd be subjecting my internet to regular clones or downloads of releases (I'm not sure how much that'd effect me generally, but it seems worth considering).

No one's internet is as reliable as a cloud hosted service either, so there's also that to consider.

So I guess a cloud option? (Codeberg probably btw)

But then (either way) you're potentially splitting a community I'd imagine?

You can mirror repos to github, but if you have a project small enough and it forces issues/prs on another service, is anyone gonna bother?

Maybe you just have to swap and be okay with less people around, just so you can get out of Microsoft's grip in open source.

Do you have any thoughts?

you are viewing a single comment's thread
view the rest of the comments
[–] starshipwinepineapple@programming.dev 2 points 2 weeks ago (1 children)

I didn't have "deeply rooted" projects, but i started by just creating new projects on codeberg. It gave me time to test it out before i moved the rest of my projects which i did ~6 months later.

For your use case i would consider the same. Figure out where you might like to migrate to and give it a test run with new projects. Then decide if you want to migrate the deeply rooted project(s) or not.

I didn't have to worry about the community much, both because i didn't have large projects and also because i was on gitlab to begin with. If anything going from gitlab to codeberg i had the same if not more engagement with my small projects. But my motivation for my migration was just wanting to use services that support what i support. For me that's what was most important in the long run.

Also re: github container registry. Forgejo (what codeberg uses) supports this: https://forgejo.org/docs/latest/user/packages/container/ . These images would then also show up on your project page under "packages" tab if it has been enabled

[–] dogs0n@sh.itjust.works 2 points 2 weeks ago

It's nice to hear you didn't see a drop in engagement, that gives me hope.

I think I might do as you say and make something small to try out codeberg, see if everything works for me (dev to release).

motivation for my migration was just wanting to use services that support what i support

Very true, if it works I should just do it. It's not like I'm losing paying customers hehe.

p.s. thanks for the link, I hadn't looked it up yet :)