Need advice about which tool to choose?Ask the StackShare community!
Gerrit Code Review vs GitHub: What are the differences?
What is Gerrit Code Review? OpenSource Git Code Review Tool. Gerrit is a self-hosted pre-commit code review tool. It serves as a Git hosting server with option to comment incoming changes. It is highly configurable and extensible with default guarding policies, webhooks, project access control and more.
What is 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.
Gerrit Code Review and GitHub are primarily classified as "Code Review" and "Code Collaboration & Version Control" tools respectively.
Some of the features offered by Gerrit Code Review are:
- git repository hosting
- pre-commit code review
- commenting on diffs
On the other hand, GitHub provides the following key features:
- Command Instructions
- Source Browser
- Git Powered Wikis
"Code review" is the top reason why over 6 developers like Gerrit Code Review, while over 1750 developers mention "Open source friendly" as the leading cause for choosing GitHub.
Airbnb, Netflix, and Medium are some of the popular companies that use GitHub, whereas Gerrit Code Review is used by Citrix, Midokura, and Wonga.com. GitHub has a broader approval, being mentioned in 4713 company stacks & 6095 developers stacks; compared to Gerrit Code Review, which is listed in 11 company stacks and 6 developer stacks.
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?
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?
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.
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.
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!
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.
Pros of Gerrit Code Review
- Code review13
- Good workflow11
- Cleaner repository story10
- Open source9
- Good integration with Jenkins9
- Unlimited repo support5
- Comparison dashboard2
Pros of GitHub
- Open source friendly1.8K
- Easy source control1.5K
- Nice UI1.3K
- Great for team collaboration1.1K
- Easy setup865
- Issue tracker504
- Great community485
- Remote team collaboration481
- Great way to share451
- Pull request and features planning442
- Just works146
- Integrated in many tools132
- Free Public Repos120
- Github Gists115
- Github pages111
- Easy to find repos83
- Open source62
- It's free60
- Easy to find projects60
- Network effect56
- Extensive API49
- Developer Profiles34
- Git Powered Wikis32
- Great for collaboration30
- It's fun24
- Clean interface and good integrations23
- Community SDK involvement22
- Learn from others source code20
- Because: Git16
- It integrates directly with Azure14
- Standard in Open Source collab10
- Beautiful user experience8
- It integrates directly with Hipchat8
- Easy to discover new code libraries7
- Smooth integration6
- It's awesome6
- Nice API6
- Cloud SCM6
- Hands down best online Git service available5
- CI Integration5
- Quick Onboarding5
- Remarkable uptime5
- Security options4
- Simple but powerful4
- Loved by developers4
- Easy to use and collaborate with others4
- Version Control4
- Unlimited Public Repos at no cost4
- Uses GIT4
- Free HTML hosting4
- Nice to use3
- Free private repos2
- Issues tracker2
- Easy deployment via SSH2
- Easy source control and everything is backed up2
- IAM integration2
- Easy and efficient maintainance of the projects2
- All in one development service2
- Good tools support2
- Free HTML hostings2
- Self Hosted2
- Never dethroned2
- Very Easy to Use2
- Easy to use2
- Leads the copycats2
Sign up to add or upvote prosMake informed product decisions
Cons of Gerrit Code Review
Cons of GitHub
- Owned by micrcosoft53
- Expensive for lone developers that want private repos37
- Relatively slow product/feature release cadence15
- API scoping could be better10
- Only 3 collaborators for private repos8
- Limited featureset for issue management3
- GitHub Packages does not support SNAPSHOT versions2
- Does not have a graph for showing history like git lens2
- Have to use a token for the package registry1
- No multilingual interface1
- Takes a long time to commit1
Sign up to add or upvote consMake informed product decisions
What is Gerrit Code Review?
What is GitHub?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Gerrit Code Review?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Gerrit Code Review?
What tools integrate with GitHub?
Sign up to get full access to all the tool integrationsMake informed product decisions