I've released my Github Action for Umbraco Cloud Deployments. Its a fully comprehensive action to deploy to Umbraco Cloud via CI/CD v2 with all sorts of utilities such as - Flexible environment deployments - Automated PR generation for Cloud Changes - Get the rej files back to manually resolve if the action can't merge Umbraco Clouds patch - Private Custom NuGet Feed injection support - File removal built in to make deployment zips to cloud smaller for cleaner repos in Umbraco Cloud No need to have lots of PowerShell/bash scripts dotted around your various cloud projects! Just reference the action in your YAML and it will handle the deployment to Umbraco Cloud. GitHub makes it painless to use the latest version of the action so new improvements added are automatically used by anyone who uses it! You can find it here: https://github.com/marketplace/actions/umbraco-cloud-deployment-action You can find some screenshots of it in action on the forum here: https://forum.umbraco.com/t/released-my-github-action-for-umbraco-cloud-deployments/7445 Let me know if there is any issues with it. We have been using this heavily at Crumpled Dog to handle all our deployments to Cloud.

What's the biggest changes/wins Matt compared to the one given from the docs by HQ currently?

Please correct me if I am wrong I haven't touched their scripts for ages as I have been continuously working on my action. Of the top of my head and quickly looking at the PowerShell. - The main benefit for me is not having 7*(the number of repos you have) of PowerShell scripts sitting in your org! This is impractical to maintain. - It requires you to be on top of what Umbraco adds to the scripts. With the action you either stay on a specific version or you can always stay on the latest of a major. - It doesn't inject a custom nuget feed into nuget.config. We use private nuget feeds by using cloud secrets for the PAT. - Apply patch doesn't generate a GitHub PR from what I can tell. Just commits directly to the branch? - Apply patch doesn't give you an artifact if it fails to apply the patch. You will have to either dig it from logs or call the API yourself - Upload artifact does not have retry logic if the first attempt fails - It doesn't give the option to clean the final deployment artifact. For example Umbraco Cloud doesn't need your front end build project just the generated css and js. This reduces the size of the repo in Cloud - It doesn't say #h5yr at the end

> It doesn't say #h5yr at the end Awww... 🥹

Nice Matt 🥰 - I hope you showed the HQ team this that they either suggest people use yours As this sounds neat (especially the PR for inbound stuff from Cloud)

They are aware of it! I was kindly offered a free Cloud Plan to test/iterate it with flexible environments etc, in its infancy before rolling it out to all our cloud sites at Crumpled Dog. Its been working well for our projects so far and I have ironed out a lot of edge cases. I don't think Umbraco wanted to add it to the docs at least not at the time I was working on it... I am anxiously awaiting for lots of GitHub issues to be raised 😳 or people to say it works well ?

I have mentioned it at the gig I am at - will see if I can get them to use it

Let me know if the README needs some more work. Looking back on it. it could be more clear?

But setting this up in YML rather than a ton of PS1 files has gotta be better for HQ and Developer Experience

What I am working towards next is moving my blog to v17 so this can be used publicly (as I understand in v17 there is no need for secrets in the umbraco file). it should help people set it up and see it in action.

Look forward to seeing/trying it

I really want to try this out! It looks very promising indeed 🎉

Let me know how it goes!