0d5bd5dcbf
All checks were successful
PR build (required check) / build-backend (pull_request) Has been skipped
PR build (required check) / build-frontend (pull_request) Has been skipped
PR build (required check) / gate (pull_request) Successful in 2s
PR build (required check) / changes (pull_request) Successful in 6s
secrets-guard / encrypted (pull_request) Successful in 5s
PR build (required check) / validate-observability (pull_request) Has been skipped
In a path-filtered monorepo the branch tip is often another domain's commit: a push tipping at an infra-only change made every backend deploy (push-triggered or dispatched) compute sha-<tip> and go looking for an image no build ever produced -- 5 minutes of pull retries, then a red run (this bit backend-deploy-prod on the release tip today). Build and deploy now compute the SAME key: git log -1 -- <domain>/, the last commit that actually touched the domain. Builds tag with it, deploys pull it, dispatches always resolve, and re-pushes of unrelated commits are naturally idempotent (same key -> image already exists). Deploy workflows gain a fetch-depth:0 checkout -- a depth-1 clone can't see past an unrelated tip to find the key. |
||
|---|---|---|
| .. | ||
| backend-build-push.yml | ||
| backend-deploy-dev.yml | ||
| backend-deploy-prod.yml | ||
| backend-deploy.yml | ||
| build.yml | ||
| frontend-build-push.yml | ||
| frontend-deploy-dev.yml | ||
| frontend-deploy-prod.yml | ||
| frontend-deploy.yml | ||
| infra-sync.yml | ||
| observability-validate.yml | ||
| ops-cron.yml | ||
| pr-build.yml | ||
| secrets-guard.yml | ||