The feature I think I would most like to see is support for patches as a more first-class object. For example reverts and cherry picks have no real metadata. This leads to conflicts when merging branches that have cherry picks (although they often auto-resolve if they are exactly the same diff) and makes asking "Does $branch contain $patch" basically impossible to answer. https://pijul.org/ greatly improves this... - Source: Hacker News / 11 days ago

In Pijul, conflicts are not modelled as a "failure to merge", but rather as the standard case. Specifically, conflicts happen between two changes, and are solved by one change. The resolution change solves the conflict between the same two changes, no matter if other changes have been made concurrently. Once solved, conflicts never come back. - from https://pijul.org/. - Source: Hacker News / 3 months ago

Do not try and bend the spoon, that's impossible. Instead, only try to realize the truth...there is no spoon. Then you will see it is not the spoon that bends, it is only yourself -- what Pijul users say when they overhear git users arguing with each other about monorepos. https://pijul.org/. - Source: Hacker News / 3 months ago

I believe that handling merges like this correctly was a motive for designing pijul: https://pijul.org See the item on the splash page about 'merge correctness'. Unfortunately I wasn't able to find the post detailing the behavior with a bit of searching. - Source: Hacker News / 4 months ago

Darcs [0] patch theory was a predecessor to OTs/CRDTs (and a predecessor to git as well; in some ways it is the "smart" to which git was named "dumb"). When it works and performs well it is still sometimes version control magic. Pijul [1] is an interesting experiment to watch, trying to keep the patch theory flag flying and also trying to bring in updates from OTs and CRDTs as it can. [0] https://darcs.net [1]... - Source: Hacker News / 4 months ago

Also for my last employer, I contributed to their private repo by building a web app that can allow People team to orchestrate IT on/off boarding tasks similar to a tool like (BetterCloud) but built in house. Source: over 1 year ago

It's also called "SaaS management" or "software asset management" e.g. zylo.com bettercloud.com or blissfully.com. Source: over 2 years ago

Many mid-to-large sized organizations use BetterCloud to manage their Google Workspaces. If you use many SaaS products, you can probably manage most of them through their platform. Source: over 2 years ago