You mean the thing that was only suitable for real world use by in-the-wild development teams last year? Something no repo provider really fully supports even to this day?

From HG's own documentation (https://www.mercurial-scm.org/wiki/ChangesetEvolution):

>While well on the way, the full implementation of the changeset evolution concept is still in progress.

HG's entire system requires far more investment in the tool than git will ever ask of you. And you probably don't need the feature in the first place. I consider changeset evolution a nifty feature, but it's also a devop smell in my book.

Changeset evolution has had the "beta" label for way too long. I started using it years ago and it was fine.

As far as smells go, its whole purpose is to make editing history less "smelly" than git's rebase -i followed by force push.

> I started using it years ago and it was fine.

You are not a full blown development team, and beta software works for many people. That doesn't mean it's ready for prime time.

No. Evolution was usable since 2015 at least. Supported by Bitbucket and others.

Evolution requires no effort whatsoever to maintain.