Migrating Classic Azure DevOps Pipelines to YAML with Manual Approvals

Moving classic Azure DevOps pipelines to YAML "pipelines as code" has many advantages. Pipelines can be reviewed with pull requests, and we can ensure that our code is always versioned with the exact pipeline that was used to deploy it.
However, YAML pipelines were a non-starter for many organizations, because they never had a mechanism for manual deployment approvals... until now.
In this video, I'll show you how to convert your classic pipeline to a YAML pipeline that takes advantage of manual approvals, which are now Generally Available.
Example code can be found on GitHub:
github.com/jaspecla/AzureDevO...

[@OThyme]

This is a really good walkthrough of YAML pipelines in Azure Devops I have seen, Good work

[@Jmconnell2012]

This was really helpful! Your examples matches exactly what I was trying to accomplish!

[@devips5102]

Excellent Sir I learnt and implemented following this video. Thank you Sir

[@wadatagalloway1143]

Very helpful video, thanks

[@harshashetty5683]

Very useful video 👍🏻

[@JustTheHighlights]

This was useful, thank you.

[@amsuprith]

Love it 💗

[@TechTalkWithMuke]

Hi.. Whether I should deploy to production or should use slot swap action? Which one is better option.

[@echarly7698]

Genial!!!

[@kevinstanley6049]

In classic releases I could setup a Deploy_Test stage with a post deployment approval and the setup a Deploy_Prod with a pre deployment scheduled release. This way it would wait for a manual approval and then once approved would only release at a certain time of day. I do not see how to do this here. any ideas?

[@nishanthraj8261]

Yes, I also don't see any options for setting up gates too.

[@azureNETCode]

Is there a reason why it won't allow a YAML pipe for code in "other Git" (generic)?

[@oldmemories242]

confusing.