FWIW, I found a better (it isn't the default) workflow with phabricator. If you set: "immutable_history": true In your repo's .arcconfig, it will work thi

FWIW, I found a better (it isn't the default) workflow with phabricator. If you set: "immutable_history": true In your repo's .arcconfig, it will work this way: When creating a topic branch and you "arc land", it will only put that nasty phabricator formatted commit message in the merge commit that merged the topic branch into the master/develop branch. When you just submit a review against the branch you want to land to, you simply git push, and the review message doesn't go to the repo. This gives us the best of both in that phabricator doesn't overwrite our commit messages, or rebase squash things, but we get the phabricator metadata in the repo when we want it.