@prologic@twtxt.net Hmm. 🤔

Okay, suppose you host a project using this new forge, and I want to send a pull request. What do I have to do?

@movq@www.uninformativ.de So the way this works in my design/prototype is this. You fork my repo in the app, it clones it to your own forge, follows my instance and it’s repo for updates and ping my instance to indicate “you’ve forked me”. Then when you publish changes, I can see them by pulling your instance’s feed. It all works on the same plain text principles of Tstxt itself. The feeds are “pull”-based with push-based “pings” on things like “someone forked your repo”, “a new issue has been raised against your repo”, etc.

@prologic@twtxt.net Ah, so I can’t send you a patch / PR unless I host gitxt myself?

@movq@www.uninformativ.de Ahh, no you can. Much like what we’ve built here with Twtxt / Yarn. I’m building a spec, clients can implement the spec, or you can ya know, just curl and git your way through. I’ll link the spec soon™, just need to keep refining and testing and make sure this actually works properly 😅