You’re offline. This is a read only version of the page.
26
I have a new developer starting, so I won't be the only person working on our solutions. So it was time to get serious about ALM. I found a video that was discussing the future of DevOps (Is Azure DevOps Going Away? If So, Where Do We Go? - YouTube). This convinced me that it made sense to setup my ALM with Github instead of DevOps. I was able to get the basic workflows working. I came to the community to get some pointers on how to best utilize this and I'm not seeing much activity around using Github for Power Apps ALM. How many people are using Github?
Todd
Yup, I think you've got it there. If you're not already invested in DevOps, don't start. You want to go GitHub, for sure. I did not watch that YouTube video, but from the title I am pretty sure I agree. DevOps is on its way out. It will be a VERY long road spanning over years, but eventually it will be entirely eclipsed by GitHub.
All the best investments are going into GitHub, from SCA and dependency tracking to Azure Integrations to even lesser-known things like FedRAMP status: GitHub is getting all the push, and DevOps is being allowed to slowly become inferior so devs are nudged ever so gently to the preferred solution.
Thanks @cchannon. I've worked with DevOps at a prior job, although not extensively. Sounds like if I'm just venturing into ALM and don't have any DevOps assets to try to migrate that it probably makes sense to give Github a first try. Sounds like you've either made the switch or are in the process. How's it going so far? Did you watch the YouTube link? If so, do you agree with the recommendations in it?
I have one team moving over to GitHub right now.
The power platform community has generally been slow to adopt this one (I think) because GitHub work item management has historically been such a letdown next to DevOps. No boards, no epics, no features... For a long time moving to GitHub would have meant rolling backwards in capabilities, PLUS, most pro dev teams have already made their MSDN / VS Enterprise investments and GitHub is a different license altogether. So when you put those together, it is pretty easy to see: from the perspective of a decision maker, moving from DevOps to GitHub would mean spending new money and a bunch of angry scrum masters. Then, in case that wasn't enough, migrating DevOps code is easy (Git to Git to win!), but moving the work items is a genuine nightmare if you're done any process customization at all (which everyone does). The interactive experience DevOps gives for work items is great, but the data migration is downright Lovecraftian.
Recently, however, GitHub has made huge strides; adding boards and extending the customizability of work items to where the feature gaps are not really painful anymore, and at the same time it has rocketed past ADO with static code analysis and dependency monitoring and a host of other capabilities. So teams are making the switch (myself included). Sadly, the migration nightmare of DevOps will continue to discourage lots of folks, so the transition will still take a very long time.
#1
WarrenBelz
109
Most Valuable Professional
#2
Michael E. Gernaey
82
Super User 2025 Season 1
#3
MS.Ragavendar
72
Share
Report
All responses (
Answers (
