Need advice about which tool to choose?Ask the StackShare community!

GitHub

244.2K
209.2K
+ 1
10.2K
Phabricator

224
317
+ 1
187
Add tool

GitHub vs Phabricator: What are the differences?

GitHub: Powerful collaboration, review, and code management for open source and private development projects. GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Over three million people use GitHub to build amazing things together; Phabricator: Open Source, Software Development Platform. Phabricator is a collection of open source web applications that help software companies build better software.

GitHub and Phabricator are primarily classified as "Code Collaboration & Version Control" and "Code Review" tools respectively.

Some of the features offered by GitHub are:

  • Command Instructions
  • Source Browser
  • Git Powered Wikis

On the other hand, Phabricator provides the following key features:

  • reviewing code before it hits master
  • auditing code after it hits master
  • hosting Git/Hg/SVN repositories

"Open source friendly" is the primary reason why developers consider GitHub over the competitors, whereas "Open Source" was stated as the key factor in picking Phabricator.

According to the StackShare community, GitHub has a broader approval, being mentioned in 4710 company stacks & 6091 developers stacks; compared to Phabricator, which is listed in 52 company stacks and 12 developer stacks.

Decisions about GitHub and Phabricator
Weverton Timoteo

Do you review your Pull/Merge Request before assigning Reviewers?

If you work in a team opening a Pull Request (or Merge Request) looks appropriate. However, have you ever thought about opening a Pull/Merge Request when working by yourself? Here's a checklist of things you can review in your own:

  • Pick the correct target branch
  • Make Drafts explicit
  • Name things properly
  • Ask help for tools
  • Remove the noise
  • Fetch necessary data
  • Understand Mergeability
  • Pass the message
  • Add screenshots
  • Be found in the future
  • Comment inline in your changes

Read the blog post for more detailed explanation for each item :D

What else do you review before asking for code review?

See more
Weverton Timoteo

Using an inclusive language is crucial for fostering a diverse culture. Git has changed the naming conventions to be more language-inclusive, and so you should change. Our development tools, like GitHub and GitLab, already supports the change.

SourceLevel deals very nicely with repositories that changed the master branch to a more appropriate word. Besides, you can use the grep linter the look for exclusive terms contained in the source code.

As the inclusive language gap may happen in other aspects of our lives, have you already thought about them?

See more
Weverton Timoteo

One of the magic tricks git performs is the ability to rewrite log history. You can do it in many ways, but git rebase -i is the one I most use. With this command, It’s possible to switch commits order, remove a commit, squash two or more commits, or edit, for instance.

It’s particularly useful to run it before opening a pull request. It allows developers to “clean up” the mess and organize commits before submitting to review. If you follow the practice 3 and 4, then the list of commits should look very similar to a task list. It should reveal the rationale you had, telling the story of how you end up with that final code.

See more
Kamaleshwar BN
Senior Software Engineer at Pulley · | 8 upvotes · 528.1K views

Out of most of the VCS solutions out there, we found Gitlab was the most feature complete with a free community edition. Their DevSecops offering is also a very robust solution. Gitlab CI/CD was quite easy to setup and the direct integration with your VCS + CI/CD is also a bonus. Out of the box integration with major cloud providers, alerting through instant messages etc. are all extremely convenient. We push our CI/CD updates to MS Teams.

See more

Gitlab as A LOT of features that GitHub and Azure DevOps are missing. Even if both GH and Azure are backed by Microsoft, GitLab being open source has a faster upgrade rate and the hosted by gitlab.com solution seems more appealing than anything else! Quick win: the UI is way better and the Pipeline is way easier to setup on GitLab!

See more
Nazar Atamaniuk
Shared insights
on
DeployPlaceDeployPlaceGitHubGitHubGitLabGitLab

At DeployPlace we use self-hosted GitLab, we have chosen GitLab as most of us are familiar with it. We are happy with all features GitLab provides, I can’t imagine our life without integrated GitLab CI. Another important feature for us is integrated code review tool, we use it every day, we use merge requests, code reviews, branching. To be honest, most of us have GitHub accounts as well, we like to contribute in open source, and we want to be a part of the tech community, but lack of solutions from GitHub in the area of CI doesn’t let us chose it for our projects.

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of GitHub
Pros of Phabricator
  • 1.8K
    Open source friendly
  • 1.5K
    Easy source control
  • 1.3K
    Nice UI
  • 1.1K
    Great for team collaboration
  • 864
    Easy setup
  • 503
    Issue tracker
  • 484
    Great community
  • 480
    Remote team collaboration
  • 450
    Great way to share
  • 441
    Pull request and features planning
  • 145
    Just works
  • 131
    Integrated in many tools
  • 119
    Free Public Repos
  • 114
    Github Gists
  • 110
    Github pages
  • 82
    Easy to find repos
  • 61
    Open source
  • 59
    Easy to find projects
  • 59
    It's free
  • 56
    Network effect
  • 48
    Extensive API
  • 42
    Organizations
  • 41
    Branching
  • 33
    Developer Profiles
  • 32
    Git Powered Wikis
  • 29
    Great for collaboration
  • 23
    It's fun
  • 22
    Community SDK involvement
  • 22
    Clean interface and good integrations
  • 19
    Learn from others source code
  • 15
    Because: Git
  • 14
    It integrates directly with Azure
  • 9
    Standard in Open Source collab
  • 9
    Newsfeed
  • 8
    It integrates directly with Hipchat
  • 7
    Fast
  • 7
    Beautiful user experience
  • 6
    Cloud SCM
  • 6
    Easy to discover new code libraries
  • 5
    Smooth integration
  • 5
    It's awesome
  • 5
    Integrations
  • 5
    Graphs
  • 5
    Nice API
  • 4
    Quick Onboarding
  • 4
    Remarkable uptime
  • 4
    Hands down best online Git service available
  • 4
    CI Integration
  • 4
    Reliable
  • 3
    Loved by developers
  • 3
    Free HTML hosting
  • 3
    Security options
  • 3
    Simple but powerful
  • 3
    Uses GIT
  • 3
    Unlimited Public Repos at no cost
  • 3
    Version Control
  • 3
    Easy to use and collaborate with others
  • 2
    Nice to use
  • 2
    IAM
  • 2
    Ci
  • 1
    Easy and efficient maintainance of the projects
  • 1
    Good tools support
  • 1
    Beautiful
  • 1
    Free HTML hostings
  • 1
    Self Hosted
  • 1
    All in one development service
  • 1
    Easy to use
  • 1
    Easy source control and everything is backed up
  • 1
    Leads the copycats
  • 1
    Never dethroned
  • 1
    IAM integration
  • 1
    Issues tracker
  • 1
    Very Easy to Use
  • 1
    Easy deployment via SSH
  • 1
    Free private repos
  • 0
    Profound
  • 33
    Open Source
  • 29
    Code Review
  • 25
    Supports Git/Hg/SVN
  • 18
    Bug Tracking
  • 17
    Audit Source Code
  • 11
    Unlimited Repo Support
  • 10
    Software Engineering Platform
  • 10
    Super fast task creation
  • 9
    Flexible Project Management
  • 8
    Project Management
  • 5
    Self hosted
  • 4
    Building Better Software
  • 2
    Best Integration with Gitlab
  • 2
    Complete set for collaborating on software development
  • 1
    Powerful, Complete, Fast, Reliable and Open Source
  • 1
    Straightforward code review process
  • 1
    Workflow
  • 1
    Very effective system, does all PM & code org needed

Sign up to add or upvote prosMake informed product decisions

Cons of GitHub
Cons of Phabricator
  • 52
    Owned by micrcosoft
  • 37
    Expensive for lone developers that want private repos
  • 15
    Relatively slow product/feature release cadence
  • 10
    API scoping could be better
  • 8
    Only 3 collaborators for private repos
  • 3
    Limited featureset for issue management
  • 2
    GitHub Packages does not support SNAPSHOT versions
  • 2
    Does not have a graph for showing history like git lens
  • 1
    Have to use a token for the package registry
  • 1
    No multilingual interface
  • 1
    Takes a long time to commit
    Be the first to leave a con

    Sign up to add or upvote consMake informed product decisions