Learn how to deploy .NET Core apps to Azure with GitHub Actions

The Discussion

• 

  Using GitHub actions for processes outside of GitHub makes no sense to me. GitHub is a source control agent. Why use it as a build agent or a deploy agent or as an Azure interface? My 2 cents is to leave GitHub to do what it knows best, which is source control, code out, code in and merge. Everything else should be handled by the areas that understand those processes best, ie. .net core builds by Microsoft Build, Azure deployments by Azure. But hey, that's just me, make up your own mind.

• 

  For anything much more serious than a hamster blog I think I will stick with Azure Devops Pipelines and Releases with gated stages. At least were I have worked you can't just push to anywhere except maybe dev, and even then that may require some approval checklist or coordination with other team members or other teams. Also not liking yet another yaml file thrown into the mix.

• 

  That's cool, but I'm still missing basic functionality like ingesting and displaying test results. Multi-stage workflows, reuse/templating - any news on that?

• 

  Thank you for sharing :)

• 

  Adone123...!!!
  

• 

  @Vgrhbbfdbbv:Hi! GitHub Actions is built upon foundations that also power Azure Pipelines. The great part is that the actions themselves do the work, so the Azure team publishes the actions that deploy to Azure. For projects already on GitHub, using Actions is a natural step to keep the code and process in the same place. You are right though, this is a tool, and anyone can choose whatever tools that work best for them!

• 

  1 day ago, foofoodog
  wrote

  For anything much more serious than a hamster blog I think I will stick with Azure Devops Pipelines and Releases with gated stages. At least were I have worked you can't just push to anywhere except maybe dev, and even then that may require some approval checklist or coordination with other team members or other teams. Also not liking yet another yaml file thrown into the mix.
  

  
  Totally understand about the approval flow aspects of Pipelines. I love those as well. I hope that Actions will implement those soon! Pipelines provides a good UI on building up the YAML file for you but also in the end is just a YAML definition as well. Each provide a great benefit to those who choose either.

• 

  1 day ago

  That's cool, but I'm still missing basic functionality like ingesting and displaying test results. Multi-stage workflows, reuse/templating - any news on that?

  
  Agreed those are valuable! I don't know updates on plans for those in Actions or timeframes.

• 

  Great stuff! I liked the show format! Thank you!

• 

  This was great. I would enjoy an episode on using GitHub Actions to create/maintain your Azure infrastructure, such as creating the App Service using something like Terraform

• 

  Scott you are genius!

• 

  Really really liked this episode - great content (i.e. i've used github actions "at speed" before but never broken down the steps) so thanks. Also the longer format was great for this content. I like the chilled slow vibes of this longer episode. I'd recommend (my humble opinion only) you try a longer episode again! Thanks both!

• 

  Great stuff, thanks.
  What actions do I need to do in order to publish a ,net core with angular front end?

• 

  @moran: Assuming you mean publish to Azure, you'd use the same Azure App Service Action https://github.com/azure/webapps-deploy on your project that has the Angular/.NET core bits. I'd recommend using the `dotnet publish` command first and deploying that output using the webapps-deploy action as was shown in the video here and a sample link here: https://aka.ms/azfr/638/07