GitHub alternatives become a stack, not a single replacement
A 421-comment Ask HN thread did not settle on one GitHub substitute. It mapped the work that GitHub bundles, then assigned each part to a different tool.
Forgejo and Codeberg kept coming up for people who want a lightweight forge they can host or use as a public service; GitLab was the answer for organizations that need a familiar enterprise-shaped platform.
The useful distinction was not hosted versus self-hosted. It was whether a team needs GitHub Actions and App integrations, or merely Git repositories with dependable CI.
The migration question hides several separate choices
The request for a GitHub alternative produced a catalogue, not a winner. Forgejo was the recurring small-stack choice; Codeberg is a public Forgejo instance; GitLab was the familiar answer for teams already operating a large organization.
A developer who runs Forgejo on a private VPS said the service had needed almost no maintenance beyond shielding it from AI crawlers. Another commenter described GitLab Community Edition as the closest feature match for an organization that already thinks in GitHub-sized workflows.
The hard dependency is often automation
The thread turned when people asked about GitHub Actions specifically. Source control is portable; a repository’s surrounding automation and app integrations can be the expensive part of leaving. One answer made the trade explicit: teams that only need local tests can keep a second Forgejo remote, while teams embedded in Actions need to price the migration of their pipelines too.
A backup remote is a practical first move
Several replies treated departure as a reversible operational decision rather than a declaration of independence. Mirroring a repository to a self-hosted Forgejo instance preserves an exit path without forcing a company to replace every integration at once. The thread’s answer was therefore less "replace GitHub" than "separate the forge, CI, and organizational plumbing before choosing."
Get breakdowns like this every day
The top Hacker News stories, unpacked — by email, Telegram, or RSS.
Cloudflare analytics injection exposes the proxy trust boundary
An HTML-only site owner found a Cloudflare analytics script in the delivered page. The debate quickly became about configuration, consent, and what a reverse proxy is technically able to change.