My company has used Phabricator, which is an alternative to Azure Devops, for about 5 years. A few days ago they announced that the project won't be maintained anymore, so we are looking into alternatives. We have around 50 devs+product folks that use Phabricator at the moment. Source: about 3 years ago

You also mention Gitlab is close to what you would like - maybe Phabricator is even closer: https://phacility.com/phabricator/. Source: about 3 years ago

Https://phacility.com/phabricator/ I think checks most of those boxes, maybe all. Source: about 3 years ago

IMO Open Source software communities are where folks like you can really thrive. They're much closer at something like a meritocracy than traditional workplaces. > I want to make the next-gen version control system While you certainly could invent one yourself, you could consider contributing to popular ones like git/mercurial. It'd help teach you both the positive and the negative aspects of their design... - Source: Hacker News / 13 days ago

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 / about 1 month 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 / 4 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 / 4 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 / 5 months ago