comments (10)

  • This is evidently not a popular opinion, but git repositories don’t need to be hosted on any platform. Your local repo is a complete copy and can be pulled and pushed from and to. If you really want a backup or “source of truth” copy, you can clone it anywhere you have shell access. We make so many simple things hard unnecessarily.

    ryandrake

  • It depends on what you are looking to get out of the next platform.

    For me, I'm not interested in the social aspect of coding anymore, so I have a Synology NAS running a git server accessible via ssh and I push my code there.

    I use klaus (https://github.com/jonashaag/klaus) as a read only git web ui. My NAS is connected to my tailscale network so it's easy to view things on the go. It's a simple setup and works great.

    jasonriddle

  • I think one important factor would be still being able to interact with a community of people who care for software and would like to put genuine thoughts. Whether it be for submitting bug reports, issues, PRs or security reports. Of course other platforms are not diverse as GitHub, it would be nice to see which other platforms are attracting such people. This in turn has a higher chance of interacting with such people.

    ciwolex

  • New repository settings for configuring pull request access [feb13-2026]

    https://github.blog/changelog/2026-02-13-new-repository-sett...

    rolph

  • Anywhere you accept unvouched pull requests will end up being spammed. You might find some respite at other sites, but whether you stay or go: you’re better off disabling pull requests on your projects for everyone but you, and then using discussions (like ghostty) where people petition to work on a feature; if they can convince you it’s a feature that’s valuable to you, then you can pull from their branch (like Linus) and merge them yourself when ready. That will halt the PRs and give you a much reduced pool of noise, as most fly-by-night sloppers won’t be interested in spending the extra tokens on both code and discussion. (You’ll still get entitled human beings who demand you add and maintain their solution to their needs, but that’s much easier to sift out and discard once people have to discuss their needs in written words rather than code.)

    altairprime

  • sourcehut.org would be my choice. Drew is pretty adamant about stuff and his morales. You will dislike somethings (UI and some policies) but will like majority of the things (tech like CI/CD etc). It's OSS and can be self-hosted as well. But I think drew fighting LLM scrappers on our behalf is good for us. It's also cheap and should progressively improve going forward.

    It's my long term plan. And the project and company is setup in a way to be here for the long game. So, I am progressively moving my projects (private and in small numbers, but still...) from gitlab to sourcehut over this year or next.

    Link - https://sourcehut.org/

    unsungNovelty

  • Git is pretty simple to host yourself. For literally decades I've used git and gitolite to host git for me and a revolving team of developers.

    But if you want it to be public though where anyone can access/fork it then you have to deal with "spam".

    comrade1234

  • Codeberg.org is really great.

    Also I recommend self-hosting Gitea for private projects and backing-up public projects

    senorcrab

  • Related question, is there a web-based self-hosted git replacement that's _light-weight_ (i.e. resilient to scraping)? Should have things like file view, file browser, etc but is not taxing on the server.

    cobertos

  • You can disable PRs and Issues on GitHub. Though still good to migrate away for reliability considerations.

    xeonmc