Hacker News new | ask | show | jobs
by wilsonthewhale 1844 days ago
As others have mentioned, this is a shame. I found the Phabricator review model much more flexible and easy to work with than GitHub and Github-clone workflows.

It's basically the traditional ultra-scalable mailing-list + patches workflow, but with very nice tooling and UI on top.

I'm going to miss it when I leave FB some day.

1 comments

as an addon, I'd love to see more organizations try to tackle this problem without just lifting the flawed GitHub model.
I have no experience with phabricator but it sounds like sourcehut - are you familiar with that one?
It's similar, but Phabricator patches are submitted via API to Differential instead of to a mailing list. Phabricator provides Arcanist (arc) to interact with its API from command-line, but some projects has their own tooling around it (e.g. Mozilla uses moz-phab as a wrapper around Arcanist).

Though I think the main selling point of Phabricator is its issue tracker (Maniphest). It is very, very, very nice. May be even the best in class. The company I'm working for switched to JIRA and we still miss Phabricator's.