Looking Back on Phabricator for Code Review

#1

Post by davidgomes » Sun, Feb 22, 2026, 2:34 PM UTC

Looking Back on Phabricator for Code Review
davidgomes.com

Re: Looking Back on Phabricator for Code Review

#2

Post by starkparker » Sun, Feb 22, 2026, 10:26 PM UTC

I loved Phabricator and hadn't heard about Phorge. Co-signed on all of these points.

Re: Looking Back on Phabricator for Code Review

#3

Post by tveita » Mon, Feb 23, 2026, 12:22 AM UTC

> In GitHub, you have to switch tabs (which is slow and distracting) to go between the PR summary and the code.

As a case study of Github UI friction, take merging a Dependabot PR from the PRs tab, with code approval required before merges. By my count this takes 6 clicks, and none of them approach a 'snappy' response time.

This is for mostly trivial single-line diffs. The entire thing could be 1 click - a hover preview on the PR list, and an 'approve and merge' button.

(To list them out: Click PR, "Files changed", "Submit review", "Approve", "Submit Review", "Merge")

Re: Looking Back on Phabricator for Code Review

#4

Post by chriscbr » Mon, Feb 23, 2026, 7:02 AM UTC

Does Facebook/Meta still use Phabricator or Phorge directly? Or do they use a fork of one of them internally?