I'm playing around with it. I self-hosted the Tranquil PDS (personal data server, part of AT Proto), a knot (git repositories), and a spindle (CI runner) on my home server. It was all relatively easy to set up but even in the week that I was bringing it up I found bugs and then saw those bugs get fixed so they're earning the "alpha" badge on their website. I'm not using it for anything load bearing yet but I like the idea at a high-level, though it remains to be seen how well code hosting fits into the AT Proto model.
Pro-tip if you're a Tangled newbie: migrating knots and spindle on your Tangled PDS before building Bobbin?
Remember that Bobbin "is only a glorified edge index, in the graph theory sense. Additionally it has a record cache, re-filled on demand. All other data that Bobbin serves comes live from PDSes & knots."
You want to first nixery bao proxy spindle with AppRole credentials, then xrpc your punchcard via ATProto. The docs explain all of this clearly, so be sure to read them thoroughly.
FWIW, I really like what Tangled is doing and I agree that we need a federation of forges. Which is why, I am planning to use ATproto too for public repositories in the code forge I am building, https://juju.bi