3 ms·
I was a heavy user of Phabricator 2014 -> 2017. Spinning it up internally at work for code reviews. Ticketing, project management etc. It was nice that everythi
by soulnothing 8y ago
I was a heavy user of Phabricator 2014 -> 2017. Spinning it up internally at work for code reviews. Ticketing, project management etc. It was nice that everything was tied together. Wiki, code reviews, sprints, etc. It was one common application. That could easily link back to one another.
The idea of tying a repository to a specific project was great. As was being able to in-line issues directly in a pull request.
However when I went to spin up a new project, and stack for myself, earlier this year. I went through the major options and settled on GitLab. I'm doing this on the public site, with public repositories. So can't speak to the pains of self-hosting.
But phabricator I think is still a great alternative if you want to use it on site. Another benefit is being able to mix and match source control systems