Why does the Phabricator workflow differ from GitHub? https://secure.phabricator.com/phame/post/view/766/write_review_merge_publish_phabricator_review_workflow/ (they favour patches over branches for features)
miniblog.
Related Posts
I'm increasingly doubtful that commit messages should be entirely immutable.
I sometimes find myself editing or commenting on merged pull requests, to help future readers.
Phabricator appended a URL to commit messages, which helped. In principle PR merging could do the same thing.
Phabricator does a great job displaying diffs. It has subword highlighting and puts the previous section (based on indentation) in the header, shown as `namespace llvm {`.
The moved line highlighting is a really nice touch too.
(screenshots of https://reviews.llvm.org/D71126)
Phabricator has 'moved line' detection in its diffs, and a comprehensible UI for it!
Source:
