31–40 of 147 posts
To clarify: this applies not just to phabricator-dot-com, but Phabricator the software: https://github.com/phacility/phabricator/commit/9ceb66453501... This is unexpected. Many companies, among them as well-resourced as Facebook, use Phabricator. I wonder if it will be forked soon by some party interested in keeping it around. OTOH it looks like none such party exists, because the public sources have not been updated…
That's a shame, heard only good things about those tools. Shameless but timely plug: I'm building a much better code review tool for teams on GitHub. Check out https://codeapprove.com and if you're interested to hear more just email me (sam at habosa dot com).
...or just use Gerrit[1], which can do everything these do out of the box, and has a much nicer workflow than GitHub once you got over the learning curve.
To clarify: this applies not just to phabricator-dot-com, but Phabricator the software: https://github.com/phacility/phabricator/commit/9ceb66453501... This is unexpected. Many companies, among them as well-resourced as Facebook, use Phabricator. I wonder if it will be forked soon by some party interested in keeping it around. OTOH it looks like none such party exists, because the public sources have not been updated…
I think Blender and KDE uses Phabricator as well.
Phabricator had seemed to be the only good product in this space when I had looked; what are people even using instead? (I guess they just put up with GitHub :/.)
Gerrit is solid: https://www.gerritcodereview.com/
Earlier quoted context omitted.
Does it still desperately want you to squash all your patches, or does it do a good job of handling an ordered stack of patches these days?
It does an excellent job handling stacks! You may be mistaking it for Phabricator, which defaults to squashing.
If you're used to the GitHub pull request style, you'd be more likely to make a small commit and add it to the request. In gerrit that approach results in a separate patch for review, which isn't what such a person would want.
(Personally, I've come to appreciate gerrit's model for strongly encouraging building patches that are encapsulated single-reviewable-changes, in a way that lends itself to never having a commit that'd break the build if you landed on it e.g. during a git bisect.... But it's also something that surprises people who've not used gerrit before, in my experience.)
Phabricator had seemed to be the only good product in this space when I had looked; what are people even using instead? (I guess they just put up with GitHub :/.)
Thanks Evan for all the work you have put in over the years. Some of my biggest learnings as an engineer have been from reading and interacting with you on the phabricator secure server and reading your code when extending phab for companies.