Member-only story
22 reasons to ditch Azure DevOps and switch to GitHub as soon as possible
As an open-source maintainer for over 15 years, and an open-source project with over 300 million downloads on NuGet, I like to think I know what it takes to have large numbers of people contribute to a code-base efficiently. Next to that, I’ve been a consultant for almost 27 years helping organizations to get the most out of modern software development efforts. As such, I regularly work with Azure DevOps (AZDO), GitHub and even BitBucket and have been able to experience their differences first-hand. In this post, I’m going to give you 22 reasons why you should switch to GitHub for your source control as soon as possible.
Collaboration
Lack of forks
I’ve written about this before, but suffice to say I care a lot about a clean source control history. Having feature branches mixed up with shared branches like main, develop, hotfix/x.x isn’t just noisy, it will often seriously obscure the visual graph of your commit history. The obvious solution to that is to use personal forks and create pull requests to bring your changes back into the main repository. AZDO does support a form of forks, but they are really just additional repositories in the same project as the main repo. It clearly was an afterthought. Just imagine a project with 50 developers. Compare this to Github where forks are completely hidden unless you look for them.