Overview

GitHub

Stacks296.5K

Followers259.0K

Votes10.3K

Azure DevOps

Stacks2.8K

Followers2.9K

Votes249

Azure DevOps vs GitHub: What are the differences?

Introduction

In this article, we will discuss the key differences between Azure DevOps and GitHub. Both Azure DevOps and GitHub are widely used platforms for software development and collaboration. While they share similarities, there are distinct differences that set them apart. Let's explore these differences in detail.

1. Integration of Tools: One of the key differences between Azure DevOps and GitHub is the integration of various tools. Azure DevOps provides an all-in-one platform that includes features like version control, build management, release management, and project planning. On the other hand, GitHub is primarily a version control system that integrates with other tools like Continuous Integration and Deployment systems. This means that Azure DevOps offers a more comprehensive solution with built-in tools, whereas GitHub relies on integrations for additional functionalities.

2. Licensing and Pricing Model: The licensing and pricing models of Azure DevOps and GitHub also differ. Azure DevOps offers different pricing tiers based on the size and requirements of the organization, with options for per-user licenses or concurrent licenses. GitHub, on the other hand, provides a freemium model, with free access for public repositories, and paid plans for private repositories. This difference in pricing models cater to different needs and budgets of organizations.

3. Extensibility and Community Ecosystem: Another significant difference between Azure DevOps and GitHub is the extensibility and community ecosystem. GitHub has a vibrant community and ecosystem, with a wide range of open-source projects, third-party integrations, and extensive documentation. It allows users to easily contribute to projects and leverage community-driven innovation. Azure DevOps also offers extensibility through its Marketplace, but it does not have the same level of community involvement and open-source presence as GitHub.

4. Release and Deployment Pipelines: Azure DevOps and GitHub differ in their approach to release and deployment pipelines. Azure DevOps provides robust features for managing automated build and release pipelines. It allows for deep integration with Azure cloud services and supports a wide range of deployment targets. GitHub, on the other hand, relies on integrations with separate CI/CD tools like Jenkins or Azure Pipelines for managing release and deployment pipelines. This means that Azure DevOps offers more native capabilities for end-to-end release and deployment management.

5. Project Management and Planning: Azure DevOps offers comprehensive project management and planning features, including backlog management, sprint planning, and task tracking. It allows for seamless integration between development and project management activities. GitHub, on the other hand, focuses primarily on version control and collaboration, with limited project management features. While GitHub's issue tracking system is powerful, it may not offer the same level of project management capabilities as Azure DevOps.

6. Enterprise-level Support and SLAs: Azure DevOps and GitHub have different levels of enterprise-level support and Service Level Agreements (SLAs). Azure DevOps offers enterprise-grade support with guaranteed SLAs for critical issues, and it is tightly integrated with Microsoft's customer support infrastructure. GitHub, on the other hand, provides support through its GitHub Enterprise offering, which includes additional features like advanced auditing and security controls. The level of support and SLAs provided by Azure DevOps and GitHub cater to different enterprise requirements.

In summary, the key differences between Azure DevOps and GitHub lie in the integration of tools, licensing and pricing models, extensibility and community ecosystem, release and deployment pipelines, project management and planning features, and enterprise-level support. Understanding these differences will help organizations choose the right platform based on their specific needs and requirements.

Advice on GitHub, Azure DevOps

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.18M views1.18M

Comments

Detailed Comparison

GitHub	Azure DevOps
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.	Azure DevOps provides unlimited private Git hosting, cloud build for continuous integration, agile planning, and release management for continuous delivery to the cloud and on-premises. Includes broad IDE support.
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	Agile Tools: kanban boards, backlogs, scrum boards; Reporting: dashboards, widgets, Power BI; Git: free private repositories, pull requests; Continuous Integration: automated builds and diagnostics; Cloud build agents: cross-platform agents for Windows, Mac and Linux; Testing Tools: unit testing, load testing, manual, exploratory and user acceptance testing; Release Management: automate deployments, gated approval workflows, audit trails; Marketplace: extensions for the Visual Studio family of products; Package Management: host npm and NuGet packages; IDE Support: Eclipse, IntelliJ, Xcode and Visual Studio; Integration: link code and releases to work items, builds, and test results
Statistics
Stacks 296.5K	Stacks 2.8K
Followers 259.0K	Followers 2.9K
Votes 10.3K	Votes 249
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 56 Complete and powerful 32 Huge extension ecosystem 27 Azure integration 26 Flexible and powerful 26 One Stop Shop For Build server, Project Mgt, CDCI Cons 8 Still dependant on C# for agents 5 Many in devops disregard MS altogether 5 Half Baked 4 Capacity across cross functional teams not visibile 4 Jack of all trades, master of none
Integrations
Grove Lighthouse Airbrake Codeship Bugsnag BugHerd Visual Studio Code HipChat CopperEgg Nitrous.IO	Visual Studio Docker Slack Trello Git IntelliJ IDEA Jenkins Octopus Deploy Eclipse Tower

What are some alternatives to GitHub, Azure DevOps?

Trello

Trello is a collaboration tool that organizes your projects into boards. In one glance, Trello tells you what's being worked on, who's working on what, and where something is in a process.

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.

Asana

Asana is the easiest way for teams to track their work. From tasks and projects to conversations and dashboards, Asana enables teams to move work from start to finish--and get results. Available at asana.com and on iOS & Android.

Basecamp

Basecamp is a project management and group collaboration tool. The tool includes features for schedules, tasks, files, and messages.

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

Confluence

Capture the knowledge that's too often lost in email inboxes and shared network drives in Confluence instead – where it's easy to find, use, and update.

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.

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.