Fossil doesn’t have GitHub PR capabilities per-se. But its design philosophy is different with a focus on smaller groups of devs and not so much drive-by patches. I think in the case being discussed for AI agents, it can be simplified.
If you want human review on the code I’m thinking keep it simple and just review in branches/tags before merging OR even just have loose patch files.
As we’re seeing with resurgence of command-line utility by agents, that extends equally well to the O.G. diff/patch. A PR is literally just a diff with commentary and an approval process prior to merging. Diffs can be attached to forum topics and so-forth.
Lots of possibilities, but I think the main thing discussed here is how is version control better suited to AI agents moving forward.
If you want human review on the code I’m thinking keep it simple and just review in branches/tags before merging OR even just have loose patch files.
As we’re seeing with resurgence of command-line utility by agents, that extends equally well to the O.G. diff/patch. A PR is literally just a diff with commentary and an approval process prior to merging. Diffs can be attached to forum topics and so-forth.
Lots of possibilities, but I think the main thing discussed here is how is version control better suited to AI agents moving forward.