I'm a few months into my experiment with doing OSS development without any use of GitHub whatsoever, and while I had to introduce a minor exception, it's mostly been quite successful. Difficult, but successful.

Tricks I've found:
- Spend money. Maybe not a hell of a lot, but more than zero. What GitHub provides is subsidized in the interest of locking you in. Going without GH means spending some cash.
- Have friends. None of this would be possible without friends lending me infrastructure.

- Be OK with less. There's a lot of features GH provides that I really don't actually use, and so it's OK to go without them.

All in all, I think that as a community, we never should have gotten to where GitHub was an SPOF for all of OSS, but it is possible to undo that. It's harder than it should be, but it's getting easier thanks to groups like Codeberg and people like @whitequark.

@xgranade one thing that's really common with switching to open alternatives in general (not just github) is when people take what they're used to and demand that the replacement work the same way

it just ends up frustrating and unnecessarily limiting; you can treat this as an opportunity to re-evaluate your assumptions and maybe realize that there's a simpler way to do things that the old system was obscuring from you

@technomancy @xgranade GitHub Actions are awful, if for whatever reason that’s your sole reference for what CI is, you’re going to do yourself a favor by moving away from GitHub.
@c0dec0dec0de @xgranade GH actions is definitely the biggest thing stopping me from moving off. what do you use to replace it?