Most relays impose pretty strict size limits on events.
I hope you know I’m not hating on your idea, I’m more curious how you’re handling it - I know jack about Go, so it’s not very easy to read your source and piece it together.
Discussion
The size limit will be a problem for non-code files. The blobs would have to be split or relays would have to accept larger events (but having "big event" relays is still infinitely better than a git server).
Git internals are *really* well designed and it makes git almost perfectly suited to exist as nostr events if we are only talking about code, so I'm going to focus on that first and then deal with "large" files if people start actually using it.
For codebases without images or binary files etc, I think it's very doable because of the way that git packs blobs. I tested it with the Bitcoin repo and it's looking very promising even on relays with the usual size restrictions (but the sheer number of events is a bit of an issue).
Could the files be stored across relays, and accessed when needed. Eg. Flie a on relay z1, file b on relay z2 etc and hyperlinked like a wiki to remain connected?
I had thought of websites built this way so the relays would share the load. The idea came from what beaker browser was attempting to do.