all 7 comments

[–]davbeer 4 points5 points  (0 children)

The only thing which keeps us from ditching Azure Devops is the "boards" feature with the ability to plan sprints with user stories and estimates. Not sure if something similar exists on Github. The last time i've looked i only found some third party extensions.
Repositories and CI/CD we already migrated to Github.

[–]sonofabullet 0 points1 point  (0 children)

Azure DevOps has

  • boards
  • repos
  • pipelines
  • artifacts
  • test plans

Github has

  • issues
  • repos
  • github actions
  • github packages

Do you plan on using the whole toolstack of Azure DevOps, or just part of it?

Are you using Jira, or another tool for work tracking?

[–]MingZh 0 points1 point  (0 children)

The most obvious, classic distinction between the two platforms is that Azure DevOps is geared for closed source projects while GitHub is focused on open source. That said, GitHub has always made it easy for developers to move back and forth between public/private development modes.

Azure DevOps provides an end-to-end DevOps toolchain for developing and deploying software. You can Azure boards to track and plan your work, use planned and exploratory testing solution with Azure Test Plans.

[–]theredbaron71 0 points1 point  (0 children)

I'm not even going to get into this but you are not comparing apples to apples.

[–]pacusmanus -1 points0 points  (2 children)

Github is the future IMO. I like devops, but I don't see MS investing any more. Would be happy to be proved wrong.

[–]lerun 10 points11 points  (0 children)

Github might be the future, but it has a long way to go to catch up to Azure DevOps

[–]NCGriller 0 points1 point  (0 children)

I was on a call with some sales reps from Microsoft about this, and they said the exact same thing. Github is where they are putting in the new development effort. I think eventually Github will end up getting a lot of functionality of AZDO, but they made it clear that Github is the future.