Need advice about which tool to choose?Ask the StackShare community!
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.
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 Azure DevOps
- Complete and powerful56
- Huge extension ecosystem32
- Azure integration27
- Flexible and powerful26
- One Stop Shop For Build server, Project Mgt, CDCI26
- Everything I need. Simple and intuitive UI15
- Support Open Source13
- Integrations8
- GitHub Integration7
- One 4 all6
- Cost free for Stakeholders6
- Project Mgmt Features6
- Crap5
- Runs in the cloud5
- Agent On-Premise(Linux - Windows)3
- Aws integration2
- Link Test Cases to Stories2
- Jenkins Integration2
- GCP Integration1
Pros of GitHub
- Open source friendly1.8K
- Easy source control1.5K
- Nice UI1.3K
- Great for team collaboration1.1K
- Easy setup867
- Issue tracker504
- Great community486
- Remote team collaboration482
- Great way to share451
- Pull request and features planning442
- Just works147
- Integrated in many tools132
- Free Public Repos121
- Github Gists116
- Github pages112
- Easy to find repos83
- Open source62
- It's free60
- Easy to find projects60
- Network effect56
- Extensive API49
- Organizations43
- Branching42
- 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
- Newsfeed10
- Standard in Open Source collab10
- Fast8
- It integrates directly with Hipchat8
- Beautiful user experience8
- Easy to discover new code libraries7
- Smooth integration6
- Cloud SCM6
- Nice API6
- Graphs6
- Integrations6
- It's awesome6
- Quick Onboarding5
- Remarkable uptime5
- CI Integration5
- Hands down best online Git service available5
- Reliable5
- Free HTML hosting4
- Version Control4
- Simple but powerful4
- Unlimited Public Repos at no cost4
- Security options4
- Loved by developers4
- Uses GIT4
- Easy to use and collaborate with others4
- IAM3
- Nice to use3
- Ci3
- Easy deployment via SSH3
- Good tools support2
- Leads the copycats2
- Free private repos2
- Free HTML hostings2
- Easy and efficient maintainance of the projects2
- Beautiful2
- Never dethroned2
- IAM integration2
- Very Easy to Use2
- Easy to use2
- All in one development service2
- Self Hosted2
- Issues tracker2
- Easy source control and everything is backed up2
- Profound1
Sign up to add or upvote prosMake informed product decisions
Cons of Azure DevOps
- Still dependant on C# for agents8
- Many in devops disregard MS altogether5
- Capacity across cross functional teams not visibile4
- Not a requirements management tool4
- Half Baked4
- Jack of all trades, master of none3
- Poor Jenkins integration3
- Tedious for test plan/case creation2
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
- No multilingual interface1
- Takes a long time to commit1
- Expensive1
Sign up to add or upvote consMake informed product decisions
What is Azure DevOps?
What is GitHub?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Azure DevOps?
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
+11
+3
+2
+12
+17
+32
+12+17