This is incredibly, incredibly sad: admin.phacility.com/phame/post/vie
introduced Phabricator to me 6 years ago, and we implemented it at my company after a month-long test. It was life-changing software.
Conversation
Phab saved our asses a ton of times.
My boss would ask: "Why did we decide not to implement this feature? A customer is asking." And within 5 mins I could go from git blame to the specific task documenting why we chose not to implement something. Everything was linked.
Replying to
More importantly, Phab's code review workflow encouraged every change to be squashed into a single commit, to be rebased on top of master. It made deployments and rollbacks trivially simple: secure.phabricator.com/book/phabflavo
(This was how tasks were ALWAYS associated with one commit.)
2
The interface was also incredible for tracking development across many devs. I remember an intern sitting on a couch, writing his internship report simply by going through his Phab activity.
And I remember saving Fridays for reviewing the activity of EVERY dev in my org.
1
1
The only knock against Phab was the lack of good CI support. And I think Gitlab and Github may have finally caught up.
Phabricator was truly incredible software. I'm very sorry to see it go.
2
1
(Now I'm debating shutting down my account with them, and digging up the old Ansible playbook I wrote to install Phabricator on a server. Not sure if I want to run my own instance forever, though ...)
1
15 hours later: yeah, I now run all my projects on a self-hosted instance of Phabricator, mirrored to GitHub.
2
2
Well, this is good news:
Quote Tweet
We want to talk to people who love Phabricator and think GitHub code review needs improvement: forms.gle/PvUdXESUNVU8XT