Avoid re-deploy if nothing changed about repo-sandbox HOT 3 CLOSED

https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks#handling-skipped-but-required-checks

from repo-sandbox.

Two ways:

• NX via inputs/outputs to work out that nothing material has changed since last cache. (This assumes that the last run was cached and retrieved).
• GitHub Action workflow filtering - only apply the workflow if certain files have changed? (How does this extend to multiple deploys?)

from repo-sandbox.

Nx is already doing this via affected and cache for PR environments and int/prod respectively.

Run pnpm nx deploy:int infrastructure
 >  NX   Running target deploy:int for project infrastructure and 2 task(s) it depends on
> nx run infrastructure:"deploy:int"  [existing outputs match the cache, left as is]

We ideally still want most GitHub actions to run but the output be a no-op. This means we can still expect workflows to run but inside the workflow they optimize what to run.

We can add GitHub action filtering to the app deploy (to int and prod) workflows as desired. Most cases however Nx will work out whether or not it needs to be deployed and as such it feels redundant to add much in the way of GitHub filtering here. We can always add it if the need arises and if there is an area which Nx will re-run when it really shouldn't do.

For now given that Nx does this fairly well I will close.

from repo-sandbox.