Comment by grayhatter

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)