What alternatives to GitHub are you using?

A directory called “git” with a bunch of bare repos accessed over ssh. You don’t need to make this complicated.

Self hosted Gitea with Gitea Actions. Works like a charm for me and a team of 5.

https://tangled.sh is an atproto (same tech as Bluesky) git collaboration platform. https://blog.tangled.sh/intro

We have a more advanced PR flow (stacking, round-based reviews), jujutsu support and we just launched our new CI system. Come join! https://tangled.sh/signup. The goal is to be the new town square for collaborating with friends and open source communities.

It's built fully in the open (https://tangled.sh/@tangled.sh/core) and we have a neat little community built around it on our Discord https://chat.tangled.sh.

To me the biggest not-easily-replaceable value is the "Hub" part of GitHub. It's easy enough to stand up your own Gitea or Forgejo instance for mirroring personal Git repos, set up your own GitLab instance for more sophisticated collaboration and CI workflows, etc...but the discoverability GitHub provides in its current form, since the vast majority of repos are hosted there (or at least have some kind of mirror there) is unparalleled.

I've wanted to build a decent one since before GitHub even existed. Maybe today's news will be the impetus I finally need to start it.

For personal projects, I'm hosting them on <https://git.disroot.org/>. It's backed by Forgejo, and for my simple needs it's plenty.

For personal projects: GIT barebone repositories + Wireshark to access them from all my devices.

OSS work is mirrored to Codeberg and SourceHut. For actions I try to make sure that local builds, and cross compilation to Windows, macOS, armhf and arm64, is always working to not soley depend on Github Actions.

Private stuff: gitea on a cheap VPS. Will most likly migrate for Forgejo in the future. That stuff runs on a toaster.

Public projects: Github. Having no problem with it. Also makes me happy poisoning LLMs with my shitty code.

Personally, GitLab. Really, though, use anything that is not part of the Microsoft behemoth.

https://codeberg.org

https://GitBusiness.com

At work we use Azure DevOps ;-;

I don't have any public repos, but for private repos, I started with Gogs on a server at home, migrated to Gitea, and finally migrated to Forgejo.

the only thing I really miss from GitHub is the social bits. it's super easy to stand up cgit etc. but you miss out on actual collab features, discover etc.

I've moved the bulk of my repos from GitHub to cgit first, but now to https://tangled.sh.

I have been using local hosted gitea for years for all private projects

Self-hosted Forgejo with Forgejo Actions for CI/CD. Forgejo Actions uses a syntax similar to GitHub Actions, so it's easy to transition. For my projects, I haven't had any issues. I'd suggest setting up an instance and testing it out to see if works with your projects/workflow as a replacement for GitHub/GitHub Actions.

To the people who say "GitHub for public projects, gitea (or whatever) for private projects," can I ask why?

If you're using GitHub for your public projects, why not just use GitHub period? Genuine question here.

My general rule of thumb:

- GitHub for things I expect broad collaboration on

- SourceHut for things I just want to share (or expect contributions from a specific group that are comfortable with email git flows)

- Self-hosted for everything else. This used to be Gitea, but I've recently switched to charmbracelet/soft-serve, which fits my needs well (it's small and comparatively simple)

As other folks have noted, the social features of GitHub are hard to replicate elsewhere, but I've enjoyed SourceHut's stripped back approach.

I loved Mercurial (still do), and despite all the bad news, Google Code. And despite even more bad-mouthing, BitBucket.

See also:

Where should I host software for individual papers in 2025 now that GitHub is part of Microsoft AI? @ academia.sx

https://academia.stackexchange.com/questions/220795/where-sh...

I love gitlab.

I work on my local Linux system and that is the most update to date

Committed items are stored in 2 places:

1. anon ftp on sdf, back to using tar files via gopher, the main site

2. gitlab is a mirror and will make it easier for youngsters. FWIW, I find gitlab easier than github.

If gitlab starts going the way github did, I will delete my items on gitlab like I did on github a long time ago.

Codeberg

Was on GitLab, then I lost my 2FA and recovery codes. Pro move.

Still browsing. https://radicle.xyz looking rad, though.

Just like bots trawl the web to train AIs with, why would using different code sites be any different? If it's visible, they will still show up and scarf down the code for training material..

So, given that this will happen everywhere, does it really make a difference what MS does?

I don't know why nobody has yet said "GitLab", but it's easily the most feature-rich GitHub alternative (and self-hostable if you need that, but if you don't, why not let them pay the hosting bill for you).

git. No, really. See here for the detailed tutorial: http://mikhailian.mova.org/node/305

Sourcehut.

Self-hosted GitLab for proprietary customer projects that I don’t want in the cloud. I don’t trust GitHub’s privacy promises — if only because of the risk of my own misconfiguration. The GitLab server runs on Ubuntu Server on a NUC and is accessed via Tailscale by our very small team. No need to make it visible to the outside world.

Slow, simple, inexpensive, safe, and good enough.

I'm using srctree https://srctree.gr.ht/repo/srctree

Hopefully you'll forgive me for shilling my own project. It's a source code sharing site with a few primary goals. First, don't break the back button. I started the project right around the time github broke too many critical features in short succession. The back button, the URL bar, and ctrl+f in the code view. I also want it to be easy to use as a federated collaboration tool. Ideally you'd start your own instance locally, get a familiar GitHub like interface for submitting patches anywhere, even by email. Or if you're hosting a project, you could have an always up instance that others could connect to.

The part I've been thinking about deeply the past few days is how to improve the discoverability of peer repos and forks. I want to create something github like in terms of collaboration, but also try to incorporate some of the best lessons from mailing list based repos where it's easy to grab and try patchsets (exposed as branches) from a 'fork' without losing the value of a cannon 'upstream' and without insisting that any specific upstream is where every single commit belongs.

The whole thing is written in zig without any dependencies other than git for some of the repo management features I haven't ported yet. (and for generating git blames) If you do use it, or notice any issues, or think it's missing features do let me know. I'm currently trying to decide which is the next most important thing to hack on :)

see also https://github.com/GrayHatter/srctree if you want to subscribe to updates (still a feature srctree lacks lol)

Is Fossil able to step into the limelight yet?

I've always been fascinated by it, but it seems to be completely out of the limelight.

Gitlab is an easy way to scale things related to code. There's also this new thing Radicle.

Good old Gitlab. There is just one con: its requirements. All the rest basically guarantees that whatever feature you might need, it will be there.

All of my code is in a synology drive folder (think Dropbox, but hosted on a NAS) with continuous backup and local git in the folders. I'm the only person who works on it, so it's been fine.

+1 to Codeberg, seems like it is the best combination of familiarity and longevity. Forgejo Actions still seems incomplete, but its Woodpecker CI seems a little more mature from what I can tell. Definitely not as fleshed out as Github Actions -- a good alternative would be to mirror your repos that require Github Actions to Github, but otherwise keep repos on Codeberg.

I use SourceHut¹ to serve git for a few private projects.

I wanted to use their pages service as well to serve an SPA but their https://srht.site/limitations prevent SPAs from contacting external services I need. I get why they do that but I need my SPA to let users login to their databases and there's simply no way to do that while adhering to SourceHut's policy.

Fortunately pico.sh², codeberg³ and GitLab⁴ (not GitHub) don't have that restriction. I experimented with each of them last year. All of them worked reasonably well. Eventually I settling on GitLab which had the nicest CI/CD of the three at the time.

¹- https://sr.ht

²- https://pico.sh

³- https://codeberg.org

⁴- https://gitlab.com

gitea and jj. We are using Gitea because of contractual requirements by different clients. I think that cloud-based Git services are fine for projects where you are unwilling or unable to invest in necessary security measures.