GitHub vs Azure DevOps EXCLUSIVE interviews

[@CoderDave]

✨Question:✨ Is there any other question you have about Azure DevOps vs GitHub?

[@emanuelerogledi5504]

There is any plan to "merge" Azure DevOps and GitHub?

[@CoderDave]

AFAIK no, there is and there will be a tight integration but won’t become a “single product”

[@RX_Char_01Patti]

Very unique way of answering complicated questions makes it very easy to understand.

[@CoderDave]

Thanks!

[@michaeld9682]

Great job! Love it

[@CoderDave]

Hehe thanks, it took a lot of work to make it, but it was fun. I should make an updated version since this one is fairly dated

[@johnnguyen1655]

you came up with a great way to explain complicated things. Thanks!

[@CoderDave]

Thank you ☺️

[@yusufdur3240]

That was a great explanation way.

[@CoderDave]

Thanks ☺️ the video is quite old now, should I do an updated version? 😁

[@bruno_kdjbnaoeuthmal]

Thank you! Very creative way to explain. Really helpful!

[@CoderDave]

hehe yes I had a lot of fun doing that. But it's kinda old already, I should probably do a new one considering the latest features

[@bruno_kdjbnaoeuthmal]

​@@CoderDave I'm about to be in a meeting in a few hours to discuss exactly this subject. I was incumbent to decide our DevOps strategy for our startup and right now I'm willing to propose to continue use of GitHub for code versioning and Azure for CI/CD/project management, as you suggested in this video. Would you say something different, considering this new features? To be honest, I kinda fell that this approach is good enough for our small team needs, but I'm little concerned about the future and I would like to avoid all the troubles if we have to migrate something... The possibility to centralize the entire operation in Azure (including hosting) is fascinating, but I have this feeling that GitHub will always be more updated with the latest 'state of the art' in this matter.

[@CoderDave]

The situation is: all the investment from MS is going into GitHub. So that is your "obvious" choice for code repo, CI, some simpler-ish CD, and packages. If you need basic project Management, GitHub Issues and the new GitHub Projects should be good enough... but if you need more structured project management, then you need to integrate that with Azure Boards (I mean, you could use other tools like Jira but... I don't like it, I'd rather stay with Boards) And for CD... again, CD in Actions is "good enough" for most basic scenarios, but Pipelines is more advanced still. I personally now use GitHub almost for everything, including CD, but I have a lot of Enterprise clients which use both AzDO (Boards and YAML Pipelines) and GitHub (everything else) Hope this helps.

[@bruno_kdjbnaoeuthmal]

@@CoderDave thank you very much! Really helpful.

[@femirnhisa7765]

10:08 & 10:13 😂

[@CoderDave]

Yes my favorite moments 🤣

[@MrTaoyang1980]

you haven't compared 2 products from pricing point of view

[@CoderDave]

You are right, the fact is that the licenses scheme is very different between the two tools, plus if you start going to GitHub Enterprise then there is the negotiation part with GitHub Sales... I just didn't want to be boring :)

[@liveasawestruck2450]

The best

[@CoderDave]

Thanks ☺️

[@CoderDave]

Thanks ☺️

[@boopathyn6079]

Very nice. more information

[@CoderDave]

Happy you liked it. I did it quite few months ago, some things te slightly changes since then 😉