Overview

GitHub

Stacks295.5K

Followers259.0K

Votes10.3K

Gerrit Code Review

Stacks116

Followers223

Votes67

Gerrit Code Review vs GitHub: What are the differences?

Introduction

Gerrit Code Review and GitHub are both popular code collaboration platforms used by developers. While they share some similarities, there are key differences between the two. In this article, we will explore the main differences between Gerrit Code Review and GitHub.

1. Access Control

Gerrit Code Review provides a powerful access control system, allowing administrators to define fine-grained permissions for different actions on the codebase. This includes the ability to set up pre-commit code reviews, ensuring that no code makes it into the repository without thorough review. On the other hand, GitHub's access control options are more limited, mainly revolving around repository-level permissions.

2. Workflow

Gerrit Code Review is often used in conjunction with Git, providing a workflow that revolves around code reviews before merging changes into the main repository. It enforces a strict process for submitting changes, involving code reviews, feedback, and approvals. GitHub, on the other hand, follows a more flexible workflow, allowing developers to work directly with branches and easily merge changes into the main branch.

3. Integration with CI/CD

Gerrit Code Review provides seamless integration with various continuous integration/continuous deployment (CI/CD) systems. It allows developers to trigger automated tests and builds based on code changes, ensuring that the code is always in a deployable state. GitHub also supports CI/CD integration, but the level of control and customization is more limited compared to Gerrit Code Review.

4. Code Collaboration Features

GitHub offers a rich set of collaboration features, such as pull requests, issues tracking, and project management tools. These features facilitate communication and collaboration among team members, making it easy to discuss changes, track progress, and manage tasks. While Gerrit Code Review does offer some collaboration features, such as inline commenting, it doesn't provide the same level of comprehensive collaboration tools as GitHub.

5. Community and Ecosystem

GitHub has a vibrant and large community, making it easy to discover and contribute to open-source projects. It offers a wide range of third-party integrations, plugins, and extensions, allowing developers to customize and extend their workflows. Gerrit Code Review, on the other hand, has a smaller community and a more limited ecosystem in terms of integrations and extensions.

6. Code Ownership

Gerrit Code Review emphasizes code ownership by associating each change with a specific reviewer. This means that there is a clear accountability for code quality, as each change has a designated reviewer responsible for reviewing and approving it. In GitHub, while reviewers can be assigned to pull requests, there is less emphasis on explicit code ownership.

In summary, Gerrit Code Review offers a more structured and controlled approach to code collaboration, with powerful access control, strict workflows, and seamless CI/CD integrations. On the other hand, GitHub provides a more flexible and feature-rich environment for code collaboration, with a larger community and a wider range of collaboration tools.

🔥 Trending in Code Collaboration on StackShare

Glide

Code Collaboration

AI-assisted technical design docs

Try it View Docs Alternatives

Try

0

8

Advice on GitHub, Gerrit Code Review

Anonymous

May 25, 2020

Decided

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!

623k views623k

Comments

Weverton

CTO at SourceLevel

Jul 28, 2020

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?

944k views944k

Comments

Weverton

CTO at SourceLevel

Aug 3, 2020

Review

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?

1.19M views1.19M

Comments

Detailed Comparison

GitHub	Gerrit Code Review
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 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.
Command instructions; Source browser; Git powered wikis; Integrated issue tracking; Code reviews with inline comments; Compare view; Newsfeed; Followers; Developer profiles; Autocompletion for @username mentions	git repository hosting; pre-commit code review; commenting on diffs; updating a single commit with multiple patch sets; project-based access control; protecting repositories
Statistics
Stacks 295.5K	Stacks 116
Followers 259.0K	Followers 223
Votes 10.3K	Votes 67
Pros & Cons
Pros 1773 Open source friendly 1463 Easy source control 1254 Nice UI 1137 Great for team collaboration 868 Easy setup Cons 56 Owned by micrcosoft 38 Expensive for lone developers that want private repos 15 Relatively slow product/feature release cadence 10 API scoping could be better 9 Only 3 collaborators for private repos	Pros 14 Code review 12 Good workflow 11 Cleaner repository story 10 Open source 10 Good integration with Jenkins
Integrations
Grove Lighthouse Airbrake Codeship Bugsnag BugHerd Visual Studio Code HipChat CopperEgg Nitrous.IO	Git

What are some alternatives to GitHub, Gerrit Code Review?

Bitbucket

Bitbucket gives teams one place to plan projects, collaborate on code, test and deploy, all with free private Git repositories. Teams choose Bitbucket because it has a superior Jira integration, built-in CI/CD, & is free for up to 5 users.

GitLab

GitLab offers git repository management, code reviews, issue tracking, activity feeds and wikis. Enterprises install GitLab on-premise and connect it with LDAP and Active Directory servers for secure authentication and authorization. A single GitLab server can handle more than 25,000 users but it is also possible to create a high availability setup with multiple active servers.

Code Climate

After each Git push, Code Climate analyzes your code for complexity, duplication, and common smells to determine changes in quality and surface technical debt hotspots.

Codacy

Codacy automates code reviews and monitors code quality on every commit and pull request on more than 40 programming languages reporting back the impact of every commit or PR, issues concerning code style, best practices and security.

RhodeCode

RhodeCode provides centralized control over distributed code repositories. Developers get code review tools and custom APIs that work in Mercurial, Git & SVN. Firms get unified security and user control so that their CTOs can sleep at night

AWS CodeCommit

CodeCommit eliminates the need to operate your own source control system or worry about scaling its infrastructure. You can use CodeCommit to securely store anything from source code to binaries, and it works seamlessly with your existing Git tools.

Phabricator

Phabricator is a collection of open source web applications that help software companies build better software.

Gogs

The goal of this project is to make the easiest, fastest and most painless way to set up a self-hosted Git service. With Go, this can be done in independent binary distribution across ALL platforms that Go supports, including Linux, Mac OS X, and Windows.

Gitea

Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD. It published under the MIT license.