Work in Progress

Separate the deployment workflows into Quick and Full deploys.

Requirements

Add environmental approvers on to PROD who must approve deployments to site
- Add Sandra/PMs short term
- Add Clients long term

New workflow called Quick Deploy
Trigger on Pull Requests when auto_merge is enabled for the PR
Use the paths filter to run on requests where all the files changed are content
PRs must be targeting the main/content branch (and should have originated from there)
Workflow has several jobs in sequence
- Build
- No backstop regression
- No deployment to DEV
- Deploy to TEST
- Comment on PR that TEST is ready for review
- Deploy to PROD (will pause for approval) using TEST artifact
main/content branch should have branch protections that require:
- A PR before merging
- 'Quick Deploy` status check to succeed before merging
- Deployment to PROD to succeed before merging
How this plays out looks like:
- Dev makes changes
- Dev creates PR and enables auto merge on it
- Workflow will build and deploy to Test, then notify relevant people to check Test
- If Test looks good, relevant people approve Prod deployment
- If Prod deployment succeeds, the PR will get auto-merged into main/content

Rework existing workflows
Use the paths-ignore filter to ignore any PRs where all the files changed are content