Quick question about CI interaction and deploys from Github

[fool]

Hiya @AlexanderNZ,

There are a lot of ways to mix GHActions and Netlify.

First off, you could run things in parallel - have GH running the test, and then polling for the deploy to complete (using our API - see [Support Guide] Understanding and using Netlify's API for omse more details), before returning a status and/or publishing the deploy.

Or, you could indeed deploy from github actions using our CLI (cf Get started with Netlify CLI | Netlify Docs) - I know there is some “published” action that does that - literally runs netlify deploy - but you could bake that into your own custom action pretty easily.

However, I can tell you that unless you configure github NOT to notify us, and instead have your ACTION notify us (probably through pre-configured buildhooks rather than in the automatic way: Build hooks | Netlify Docs) that we will NOT wait for anything except that notification to start your build here!

This article also has a lot of somewhat generic test patterns that may inspire:

[Support Guide] Testing your Netlify builds

Last checked by Netlify Support Team on Sep 1, 2022. Running tests as a part of continuous deployment processes is a fantastic way to ensure that your code is indeed production ready and not prone to errors you can anticipate. Fortunately, Netlify’s build system and Deploy Previews can help make testing your application easier! I think most testing can fit into three categories: unit testing - most important during a cycle of active development, but can also be run at build time. This is m…

Let us know what you come up with