GitHubย vsย Review Board

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

GitHub

283.3K
247.3K
+ 1
10.3K
Review Board

20
52
+ 1
6
Add tool

GitHub vs Review Board: What are the differences?

GitHub and Review Board are two popular tools used in software development for managing and reviewing code changes. While both serve a similar purpose, there are several key differences between the two.

  1. Integration with Version Control Systems: One major difference between GitHub and Review Board is their integration with version control systems. GitHub is primarily designed to work with Git, a distributed version control system. On the other hand, Review Board supports various version control systems like Git, Mercurial, Subversion, and Perforce, providing more flexibility for teams using different VCS.

  2. Online Code Hosting vs. Self-Hosted: GitHub is a cloud-based platform that offers online code hosting for open-source and private projects. It provides a user-friendly interface and takes care of setting up the infrastructure for code repositories. In contrast, Review Board is a self-hosted code review tool that requires installation on a server. It provides full control over the code review process but requires more setup and maintenance efforts.

  3. Pull Request Workflow vs. Traditional Review: GitHub has a pull request workflow, where developers can create a branch, make changes, and submit a pull request for review. Reviewers can comment on specific lines of code and give approvals or suggestions before merging the changes. Review Board, on the other hand, follows a more traditional review process where reviewers manually upload diffs and provide comments. This approach allows for more flexibility, but it may require additional steps to manage the review process.

  4. Community and Collaboration Features: GitHub has a strong focus on community and collaboration features. It allows developers to easily fork, clone, and collaborate on open-source projects. It also provides social features like following users, starring repositories, and contributing to public projects. Review Board, on the other hand, is more focused on the code review process itself and does not offer the same level of community and collaboration features.

  5. Extensibility and Integration: GitHub provides a rich ecosystem of integrations and extensions. It offers a marketplace of apps and integrations that can be used to extend its functionality. This allows teams to integrate their favorite tools like build systems, project management software, and continuous integration services into their development workflow. Review Board also supports extensions, but its ecosystem is not as extensive as GitHub's.

  6. Commercial vs. Open Source: GitHub offers both free and paid plans, with additional features and support for private repositories available in paid plans. It is primarily a commercial product owned by Microsoft. Review Board, on the other hand, is open-source software and can be used and modified freely. It is supported by a community of contributors and does not require any licensing fees.

In Summary, GitHub and Review Board differ in terms of integration with version control systems, online code hosting vs. self-hosted, pull request workflow vs. traditional review, community and collaboration features, extensibility and integration options, and commercial vs. open-source nature.

Advice on GitHub and Review Board

Hi, I need advice. In my project, we are using Bitbucket hosted on-prem, Jenkins, and Jira. Also, we have restrictions not to use any plugins for code review, code quality, code security, etc., with bitbucket. Now we want to migrate to AWS CodeCommit, which would mean that we can use, let's say, Amazon CodeGuru for code reviews and move to AWS CodeBuild and AWS CodePipeline for build automation in the future rather than using Jenkins.

Now I want advice on below.

  1. Is it a good idea to migrate from Bitbucket to AWS Codecommit?
  2. If we want to integrate Jira with AWS Codecommit, then how can we do this? If a developer makes any changes in Jira, then a build should be triggered automatically in AWS and create a Jira ticket if the build fails. So, how can we achieve this?
See more
Replies (1)
Sinisha Mihajlovski
Design Lead | Senior Software Developer ยท | 1 upvotes ยท 351K views
Recommends

Hi Kavita. It would be useful to explain in a bit more detail the integration to Jira you would like to achieve. Some of the Jira plugins will work with any git repository, regardless if its github/bitbucket/gitlab.

See more
Decisions about GitHub and Review Board
Elmar Wouters
CEO, Managing Director at Wouters Media ยท | 7 upvotes ยท 544.9K views

I first used BitBucket because it had private repo's, and it didn't disappoint me. Also with the smooth integration of Jira, the decision to use BitBucket as a full application maintenance service was as easy as 1, 2, 3.

I honestly love BitBucket, by the looks, by the UI, and the smooth integration with Tower.

See more
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 ยท 688.2K 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
Manage your open source components, licenses, and vulnerabilities
Learn More
Pros of GitHub
Pros of Review Board
  • 1.8K
    Open source friendly
  • 1.5K
    Easy source control
  • 1.3K
    Nice UI
  • 1.1K
    Great for team collaboration
  • 867
    Easy setup
  • 504
    Issue tracker
  • 486
    Great community
  • 483
    Remote team collaboration
  • 451
    Great way to share
  • 442
    Pull request and features planning
  • 147
    Just works
  • 132
    Integrated in many tools
  • 121
    Free Public Repos
  • 116
    Github Gists
  • 112
    Github pages
  • 83
    Easy to find repos
  • 62
    Open source
  • 60
    It's free
  • 60
    Easy to find projects
  • 56
    Network effect
  • 49
    Extensive API
  • 43
    Organizations
  • 42
    Branching
  • 34
    Developer Profiles
  • 32
    Git Powered Wikis
  • 30
    Great for collaboration
  • 24
    It's fun
  • 23
    Clean interface and good integrations
  • 22
    Community SDK involvement
  • 20
    Learn from others source code
  • 16
    Because: Git
  • 14
    It integrates directly with Azure
  • 10
    Standard in Open Source collab
  • 10
    Newsfeed
  • 8
    It integrates directly with Hipchat
  • 8
    Fast
  • 8
    Beautiful user experience
  • 7
    Easy to discover new code libraries
  • 6
    Smooth integration
  • 6
    Cloud SCM
  • 6
    Nice API
  • 6
    Graphs
  • 6
    Integrations
  • 6
    It's awesome
  • 5
    Quick Onboarding
  • 5
    Reliable
  • 5
    Remarkable uptime
  • 5
    CI Integration
  • 5
    Hands down best online Git service available
  • 4
    Uses GIT
  • 4
    Version Control
  • 4
    Simple but powerful
  • 4
    Unlimited Public Repos at no cost
  • 4
    Free HTML hosting
  • 4
    Security options
  • 4
    Loved by developers
  • 4
    Easy to use and collaborate with others
  • 3
    Ci
  • 3
    IAM
  • 3
    Nice to use
  • 3
    Easy deployment via SSH
  • 2
    Easy to use
  • 2
    Leads the copycats
  • 2
    All in one development service
  • 2
    Free private repos
  • 2
    Free HTML hostings
  • 2
    Easy and efficient maintainance of the projects
  • 2
    Beautiful
  • 2
    Easy source control and everything is backed up
  • 2
    IAM integration
  • 2
    Very Easy to Use
  • 2
    Good tools support
  • 2
    Issues tracker
  • 2
    Never dethroned
  • 2
    Self Hosted
  • 1
    Dasf
  • 1
    Profound
  • 3
    Simple to use. Great UI
  • 1
    Review Bots
  • 1
    Diff between review versions
  • 1
    Open Source

Sign up to add or upvote prosMake informed product decisions

Cons of GitHub
Cons of Review Board
  • 54
    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
  • 4
    Limited featureset for issue management
  • 3
    Does not have a graph for showing history like git lens
  • 2
    GitHub Packages does not support SNAPSHOT versions
  • 1
    No multilingual interface
  • 1
    Takes a long time to commit
  • 1
    Expensive
    Be the first to leave a con

    Sign up to add or upvote consMake informed product decisions

    - No public GitHub repository available -

    What is GitHub?

    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.

    What is Review Board?

    Review Board is an open source, web-based code and document review tool built to help companies, open source projects, and other organizations keep their quality high and their bug count low.

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

    What companies use GitHub?
    What companies use Review Board?
    Manage your open source components, licenses, and vulnerabilities
    Learn More

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with GitHub?
    What tools integrate with Review Board?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    Blog Posts

    Dec 8 2020 at 5:50PM

    DigitalOcean

    GitHubMySQLPostgreSQL+11
    3
    2415
    GitHubOptimizelySegment+3
    4
    1185
    Mar 18 2020 at 9:12AM

    LaunchDarkly

    GitHubLaunchDarkly+2
    7
    1127
    JavaScriptGitHubReact+12
    5
    4168
    GitHubDockerReact+17
    41
    36927
    What are some alternatives to GitHub and Review Board?
    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.
    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.
    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.
    Git
    Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.
    SVN (Subversion)
    Subversion exists to be universally recognized and adopted as an open-source, centralized version control system characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations.
    See all alternatives