Live data from Hacker News

Bye, Bye GitHub

log.ozgur.works

31–40 of 80 posts

Re: Bye, Bye GitHub

#31

Earlier quoted context omitted.

Maybe for big companies that irresponsibly vendor-locked themselves, but I work at a SMB (~60 employees) and we switched to Forgejo in a couple days

I would not call it irresponsible. If you have a big, long running project you're going to want to develop complex pipelines and build processes to help with development and testing. This will save a lot of time and create a more consistent workflow, but switching vendors can require redoing work that was built over years.

>develop complex pipelines and build processes to help with development and testing. This will save a lot of time and create a more consistent workflow,

Beware the trap of making the pipeline so complicated it's like code except you can't debug or unit test like regular code, and it takes an hour between attempts to see if a change worked.

Re: Bye, Bye GitHub

#32
GitHub is going the wrong way, but there really is nothing workable for open-source projects except GitHub. I don’t want to register on all these random GitHub killers just to open an issue or PR in a random project I’ve interacted with.

For personal or team setups, any third-party service will work well.

Re: Bye, Bye GitHub

#33

IME switching git providers is very hard, especially getting off of github. Most companies have insane numbers of integrations, automations, etc on top of GH. So yeah, its on us, but its also pretty simple algebra: does GH's downtime affect us more than the cost of switching? Most companies the answer is no. When people ask why people aren't switching to Gitlab, ADO, Bitbucket, etc, I believe this is the reason.

I can't imagine anybody switching to ADO from GitHub. Microsoft has made clear that ADO is on life support, and are slowly stripping features out like public repos.

I look forward to when GitHub Actions has feature parity with Azure Pipelines.

Re: Bye, Bye GitHub

#34
With SourceHut banning projects that use LLMs[1], I’m looking to migrate this weekend.

While I can host Forgejo just fine[2], doing so means no one will be able to contribute to the projects, since federation isn’t a thing yet. Heck, getting contributions on SourceHut was hard enough, and it doesn’t even require people to register an account.

I might need to bite the bullet and go with GitHub. Regardless of what I think about the company and Microsoft, it’s where the people are.

[1]: https://sourcehut.org/blog/2026-08-27-tos-changes-and-llms/

[2]: And already do locally, as a mirror to SourceHut.

Re: Bye, Bye GitHub

#35
post #23

What frontier model did GitHub train? All of the frontier labs scraped GitHub like they scraped everything else. While GitHub has certainly tried to profit from AI, directing ire at GitHub for frontier labs training on public code seems misplaced.

Microsoft owns GitHub.

Re: Bye, Bye GitHub

#36

GitHub is going the wrong way, but there really is nothing workable for open-source projects except GitHub. I don’t want to register on all these random GitHub killers just to open an issue or PR in a random project I’ve interacted with. For personal or team setups, any third-party service will work well.

> I don’t want to register on all these random GitHub killers

You don't have to; all the GitHub killers support GitHub sign on

Re: Bye, Bye GitHub

#38
I was about to mention Codeberg but I saw the last two changes to the terms of use and they're basically digging themselves into the ground with so many restrictions

Re: Bye, Bye GitHub

#39
post #38

I was about to mention Codeberg but I saw the last two changes to the terms of use and they're basically digging themselves into the ground with so many restrictions

It’s like the restaurant that is cash only and refuses to accept credit cards. Like bruh, what?

Re: Bye, Bye GitHub

#40

IME switching git providers is very hard, especially getting off of github. Most companies have insane numbers of integrations, automations, etc on top of GH. So yeah, its on us, but its also pretty simple algebra: does GH's downtime affect us more than the cost of switching? Most companies the answer is no. When people ask why people aren't switching to Gitlab, ADO, Bitbucket, etc, I believe this is the reason.

It really is a testament to the power of mindshare and vendor lock-in. Git is GPL-licensed, the format is a de-facto standard, the commits and tags live in an on-disk format, merging and collaboration doesn't require a server, and yet somehow we still managed to end up with a centralized system with GitHub at the center.
Post reply on HN