Readit News logoReadit News
Posted by u/yakattak 4 months ago
Ask HN: What alternatives to GitHub are you using?
Lately I’ve been seeing a lot of chatter about GitHub alternatives. I’m interested in looking into them as well but I was curious what everyone else’s experience was.

I’ve been looking at Codeberg but I’m really anxious to leave GitHub Actions behind and Codeberg’s replacement doesn’t seem ready yet.

icy · 4 months ago
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.

Last night was a ton of fun with the sudden influx of users thanks to the GitHub news. :)

danielspace23 · 4 months ago
Just an fyi for everyone: while Tangled is built partly on top of ATProto, it differs from its component architecture widely, as the tasks that should be done by the AppView are offloaded to "knots", self-hostable servers specific to Tangled that do most of the Git heavy lifting. It violates the "user data stays on the PDS" principle, as repo data stay on knots, not in PDSes. As far as I know, no other ATProto application has a similiar architecture.
yjftsjthsd-h · 4 months ago
> It violates the "user data stays on the PDS" principle, as repo data stay on knots, not in PDSes.

I'm not familiar with ATProto; what does this mean in practice? Does it just change the failure modes if something breaks?

abound · 4 months ago
You piqued my interest with the mention of jujutsu support. I just read the post on using it for code review [1] for stacked PRs and was really impressed, awesome work!

I've never used Gerrit directly, but I'm guessing that Jujutsu's change IDs are like a native version of what Gerrit does there.

I regularly (attempt to) do stacked diffs on GitHub with jj, and even with a bunch of automations it's still a clunky, awkward experience.

[1] https://blog.tangled.sh/stacking

icy · 4 months ago
Glad you liked it! Yes, jj's change IDs are very similar to Gerrit's, but instead of a commit trailer it's now a header in the commit object itself. For example:

    $ git cat-file commit caa00e20


    tree e8418bf7e7c626fdf5b1570e6efcddf1e1b0c923
    parent 1e3a841997f81c9b0ed21dc5a91e783fcf2f4ec7
    author Anirudh Oppiliappan <anirudh@tangled.sh> 1754996643 +0300
    committer Anirudh Oppiliappan <anirudh@tangled.sh> 1754996799 +0300
    change-id skwlyzyomnwqntksmoqkrllqlpsskztt

    xrpc/{errors,serviceauth}: split shared xrpc code to top-level package

    Signed-off-by: Anirudh Oppiliappan <anirudh@tangled.sh>

microflash · 4 months ago
Looks very interesting. Just signed up.

A few things that would make me actually use it: - namespaces (aka, organizations in GitHub terminology) - private repos (I usually start with private repos and then make them public)

The interface is really friendly and I like how approachable it is. You should make dedicated docs site instead of throwing folks at a bunch of markdowns. Maybe create a “Pages” equivalent and demo it by building a docs site?

icy · 4 months ago
Yeah, for now orgs/namespaces are their own accounts (even better if you have a dedicated domain for your org). Private repos aren't a thing just yet since we use AT Protocol, and all data on protocol is public -- for now. This will change soon.

Appreciate the feedback! A dedicated docs site is in the works (along side a pages offering!).

aranw · 4 months ago
I'm really liking tangled.sh but I don't think it supports private repos seen as it's built on top of atproto
mozzius · 4 months ago
this is the only one really gunning for the “hub” part of github, very exciting stuff
yjftsjthsd-h · 4 months ago
> jujutsu support

What does that mean? Doesn't jj just use git as its backend?

icy · 4 months ago
We support stacked pull requests tracked using jj's change-ids: https://blog.tangled.sh/stacking
icapybara · 4 months ago
I like the design of your site. Loads very fast, looks clean.
icy · 4 months ago
Thanks! Excellent site-wide performance is something we aim for -- hence our stack of Go + htmx!
cryo · 4 months ago
Do I miss something? The site only shows a stream but nothing to describe or show the project.
moksha256 · 4 months ago
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.
Fluorescence · 4 months ago
For what specifically?

My top-of-funnel is not searching github but recommendations or searching technology/platform specific repositories e.g. for software it's flathub/f-droid and for rust its crates.io/libs.rs.

Where the code is hosted is in theory irrelevant... but I'm ashamed to say that when code turns out to be on gitlab my heart sinks. It's a bit of a red flag for e.g. no bug-tracking, no contributions, no maintenance, absent maintainer and unexpected licenses.

It's gross personal hypocrisy because I hate the absurdity of commercially owned FOSS collaboration and centralised git and happily self-host myself... but those not publishing code on github are awkward bastards :)

echelon · 4 months ago
It's 100% the network, not the tech.

You can have 1:1 parity with any company or product, but unless you have their word of mouth distribution and adoption, you will lose. Every time.

People in aggregate, as crowds, are relatively static and inflexible. Once they learn a fact once, it sticks. You cannot unteach that without lifting metaphorical mountains. The first mover with escape velocity wins.

The amount of energy needed to undo that is massive.

You'll have fringe 0.01%ers adopt some other tool, but they'll never carry enough gravitas to bring the entire network with them.

Anecdotal evidence:

- Github, Facebook, and Reddit have never been unseated

- Instagram has never been replaced, only supplemented

- Twitter/X has only lost steam due to extremely bad press, an unwanted name change, and a huge effort from Meta (which leveraged traffic and synergy from Instagram). And even then, it's still well within the public zeitgeist. Bluesky and Mastodon didn't even make dents.

- Google has never been displaced (granted, Google pays a lot of money to maintain defaults and maintain a web "pane of glass" monopoly, redefine the address bar as a search bar, etc.)

freeopinion · 4 months ago
Why should Github, Facebook, Reddit, or anybody else be unseated.

Just because I use Codeberg doesn't mean Github should die. Just because I never ever visit Facebook doesn't mean you should stop using it.

Why can't we all just play nice?

grim_io · 4 months ago
All your examples have replaced some other service in the past.

Except GitHub, maybe.

Granted, the replaced services were nowhere near the popularity levels of the current ones, and have made horrible decision.

riidom · 4 months ago
I'd like to see a federation of git-hosting instances, fediverse-style.
nerdypepper · 4 months ago
there's https://forgefed.org/ defined by the creators of forgejo. there is no complete implementation of the spec. from the last forgejo changelog, the "star" action has been completely federated. federated PRs and issues are a long way away.

https://tangled.sh is the other contender in this space that I know of. uses atproto (same as bluesky) under the hood.

fundamentally activitypub is insufficient to define these kind of networks. you'd need to have some sort of object-capability representation. the creators of forgefed are also moving in this direction: https://codeberg.org/Playwright/playwright

mhitza · 4 months ago
It's not only discoverability, but also the need for accounts.

At some point I made very tiny contributions to OSS projects that had their own Gitlab hosted instances.

Sure a password manager makes it tolerable, but what about having an anonymous way of opening up PRs (subject to owner moderation of course)?

Use the author name and email for a virtual identity and when the PR request is accepted (not merged) force an email address validation for the PRer so that comment interaction can happen via email.

xigoi · 4 months ago
This is an entirely self-inflicted problem. Git was designed so you can just send someone a patch by e-mail. It was GitHub that introduced “pull requests”, which require an account, as the main method of collaboration. Vendor lock-in as a feature.
freeopinion · 4 months ago
Or...

Fork the original repo onto your forge. Your forge could be your own forgejo instance, your own GitLab instance, just a plain git repo, or even Github if you like it so much.

Then send a note to the original authors informing them of your fork and the patch you wrote. Request that they review your work and pull it into their repo if they approve of it.

You don't need an account on their forge and they don't need an account on your forge.

dv_dt · 4 months ago
The defacto hub to search for projects and host projects has shifted before - it may be hard to believe now but at one time sourceforge was in github's position. Now that was a much earlier time in web collaborative repos but it could shift again.

Similar for indexes of open source repos - I dont know of a singlar winner now but it was for a bit freshmeat for a feed of open source project updates

dboreham · 4 months ago
Host your projects in Gitea then configure mirroring to GitHub for discoverability.
freeopinion · 4 months ago
Or submit your Gitea repo list to three or four search engines.
woodrowbarlow · 4 months ago
it depends on which network effects you want to benefit from. if you want your project to have visibility or attract contributors, then yeah. (although, mirroring your project to github can still accomplish a lot of that.) but if you want to benefit from forge tooling, like the ecosystem of github actions, then there are pretty good efforts to match API compatibility -- e.g., the gitea action runner can work with most github actions.
Catbert59 · 4 months ago
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.

lokimedes · 4 months ago
I run Gitea on my old Synology NAS, fast as a devil, especially when compared to Gitlab.
srhtftw · 4 months ago
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 settled 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

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

Deleted Comment

matths · 4 months ago
but then you don't have the pull request feature, do you?
synack · 4 months ago
You push a branch and send an email.
dboreham · 4 months ago
Software was developed before the pull request. Typically proposed diffs were emailed around. Presumably this is what the pull request is trying to emulate.
Aurornis · 4 months ago
The anti-UI people want to use e-mail and command line tools.

It’s not a direct equivalent to pull requests because it lacks all of the easy history, inline commenting, comment status tracking, and ease of use, among other things.

abound · 4 months ago
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.

0xbadcafebee · 4 months ago
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).
xigoi · 4 months ago
GitLab somehow manages to be even slower and more bloated than GitHub.
muzani · 4 months ago
They had a really nice wiki back when I was using it too.
ozornin · 4 months ago
yakattak · 4 months ago
Do you use their actions at all?
whalesalad · 4 months ago
can someone with lore knowledge share the deal between gitea, forgejo and codeberg
kbolino · 4 months ago
It actually starts with Gogs.

Gogs is FOSS but basically BDFL. What does and does not make it into Gogs (it's still around) is ultimately decided by one person, and he's fairly conservative. Gogs is very fast but lacks a lot of features that would allow it to go head-to-head with GitHub or Gitlab.

So, Gitea was forked from Gogs to allow it to take a different direction, with a larger group of maintainers and more input from the user community.

There were two major attempts to have hosted Gitea. The first was Codeberg, a nonprofit based in the EU. The second is a business that took the name Gitea, is based in the US, and changed Gitea (the software) to the "open core, closed premium" model.

This change led to the creation of the Forgejo fork, which Codeberg adopted.

woodrowbarlow · 4 months ago
gitea is the OG. forgejo is a fork, focused on lower resource needs (i think?). codeberg uses forgejo and adds static-site generation (like github pages) and CI/CD (via woodpecker).
bananapub · 4 months ago
gogs existed, gitea forked from it, gitea made some corporate structure change some people didn't like, they forked forgejo, codeberg is a hosted instance of forgejo.