Post #1780132
2026-04-29 15:55 UTC
Replies (8)
-
@jorijn@toot.community 2026-04-29 16:01
@kev doesn’t have to be a big bang. I’ve been making new repositories on Forgejo, instead of migrating everything.
-
@chartonjeremiah@fosstodon.org 2026-04-29 16:03
@kev I knew there was something wrong with Github...as soon as the company I work for started using it excessively.
-
@alextheuxguy@fosstodon.org 2026-04-29 16:19
@kev at work the GitHub outages have caused significant issues, multiple times we’ve been unable to fix production bugs due to broken pipelines, not being able to review PRs, etc. We take bets now on what time of the day GitHub will go down. I’ve started creating any new projects in Codeberg, probably won’t ever get around to migrating old projects though.
-
@Gina@fosstodon.org 2026-04-29 16:31
@kev do ittt. Codeberg is really nice. If you request access to their Woodpecker CI it's even easier.
-
@uncle@social.yolicali.mx 2026-04-29 17:34
@kev Made the same call two days ago — went straight to Codeberg, no GitHub stop. From a flat start (no account, no SSH key) the mechanics took maybe 90 minutes: OAuth signup, an ed25519 key, the ~/.ssh/config entry, creating the org, pushing a real repo. The "energy" is mostly in the framing. And Bushell's right that it doesn't have to be all-at-once — new things go to Codeberg; the GitHub mirror keeps idling. The first repo is the hardest by far.
-
@gryzor@androiddev.social 2026-04-29 19:17
@kev it's a good move. I did it a while ago. I still have a GitHub account because Microsoft of course doesn't let you browse codebases without being logged in (in a very dick move), so you kind of need one from time to time.
-
@lalalasombra@chaos.social 2026-04-29 19:42
@kev You should do it
-
@kwramm@mastodon.gamedev.place 2026-04-30 08:09
@kev Switching is pretty easy. There's a migrate option from what I remember where you just point it to your github repo and it copies it