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

Azure DevOps

2.7K
2.8K
+ 1
248
GitHub

280.5K
244.6K
+ 1
10.3K
Add tool

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.

Decisions about Azure DevOps and GitHub
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 · 672K 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 Azure DevOps
Pros of GitHub
  • 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
  • 15
    Everything I need. Simple and intuitive UI
  • 13
    Support Open Source
  • 8
    Integrations
  • 7
    GitHub Integration
  • 6
    One 4 all
  • 6
    Cost free for Stakeholders
  • 6
    Project Mgmt Features
  • 5
    Crap
  • 5
    Runs in the cloud
  • 3
    Agent On-Premise(Linux - Windows)
  • 2
    Aws integration
  • 2
    Link Test Cases to Stories
  • 2
    Jenkins Integration
  • 1
    GCP Integration
  • 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
  • 482
    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

Sign up to add or upvote prosMake informed product decisions

Cons of Azure DevOps
Cons of GitHub
  • 8
    Still dependant on C# for agents
  • 5
    Many in devops disregard MS altogether
  • 4
    Capacity across cross functional teams not visibile
  • 4
    Not a requirements management tool
  • 4
    Half Baked
  • 3
    Jack of all trades, master of none
  • 3
    Poor Jenkins integration
  • 2
    Tedious for test plan/case creation
  • 53
    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
    No multilingual interface
  • 1
    Takes a long time to commit
  • 1
    Expensive

Sign up to add or upvote consMake informed product decisions

What is Azure DevOps?

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.

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.

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

What companies use Azure DevOps?
What companies use GitHub?
See which teams inside your own company are using Azure DevOps or GitHub.
Sign up for StackShare EnterpriseLearn More

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

What tools integrate with Azure DevOps?
What tools integrate with GitHub?

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
2
2371
GitHubOptimizelySegment+3
2
1179
Mar 18 2020 at 9:12AM

LaunchDarkly

GitHubLaunchDarkly+2
7
1116
JavaScriptGitHubReact+12
5
4144
GitHubDockerReact+17
41
36556
What are some alternatives to Azure DevOps and GitHub?
Jenkins
In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.
AWS CodePipeline
CodePipeline builds, tests, and deploys your code every time there is a code change, based on the release process models you define.
Jira
Jira's secret sauce is the way it simplifies the complexities of software development into manageable units of work. Jira comes out-of-the-box with everything agile teams need to ship value to customers faster.
Visual Studio
Visual Studio is a suite of component-based software development tools and other technologies for building powerful, high-performance applications.
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.
See all alternatives