Exactly. First you are using Azure through Github actions and do all the leg work to develop Docker images, etc. to test your code. Then you start off hosting on a small free plan. Fast forward a bit and you're paying Azure $$$ because why learn all the IaaS esoterica when you can just click a button on Github.

That sounds a bit like Github Pages which has been a thing for a while.

Sure, if your site is solely static content, which is all GitHub pages supports. You can’t run “production code”.

I know some people use the service with a static site generator as a free way to host a blog, but it’s not really the same thing at all.

Works pretty good for blogs and in general if you use serverless tech.

However i wouldn't consider it for mission critical stuff - github's infrastructure can't be compared to actual paid-for cloud hosting.

> github's infrastructure can't be compared to actual paid-for cloud hosting.

I think the idea in this thread is that since github is owned by MS, and they have Azure, that won't be an accurate statement for very long. Github doesn't have to build that infrastructure, they just need to competently integrate into MS existing infrastructure.

I can't believe I didn't piece this together sooner but I agree with this threads premise. I'm already hosting my source on Github so why not build it there? And if I'm building it there then why not deploy it there? Rather than manage a complicated pipeline, I just `git push` and everything else just works ... all the way to massive scale.

As someone who has worked on hand-built github to AWS pipelines ... I can actually see this being the killer feature Azure needs to actually win a large market share.

The actual equivalent would be something like Azure AppService.