See this tool: https://discourse.pijul.org/t/git-pijul-python-module/793/ (but know that it was abandoned in favor of Darcs: https://github.com/ganwell/git-pijul/issues/2#issuecomment-1350866526 )
It would be interesting to see if that user managed to submit a bug report about the “insistent repos” (did they mean “inconsistent” there?).
Hi, I am new to pijul, but think it is really cool!
I was thinking, being on a large team, it would be hard to convince everyone to use the different VCS instead of git. But If I could use pijul alongside git to do the heavy-lifting of merges and patches, then it is an easier way to integrate pijul into my workflow.
I am not proposing pijul “knows” anything about git necessarily, but just that you would have a repo that is both a git repo and a pijul repo. And you could use the unique tools of pijul to help with the some aspects of VCS.
Mostly, I am wondering, does this kind of workflow make sense? And if so, it would be useful to have a guide for something like this.