Ronni Baslund
4907d0a856
ci / changes (push) Successful in 3s
ci / tc_booking (push) Successful in 22s
ci / tc_portal (push) Successful in 23s
ci / tc_platform_api (push) Successful in 21s
ci / tc_operator (push) Successful in 24s
ci / tc_website (push) Successful in 22s
ci / test_platform_api (push) Successful in 33s
ci / build_booking (push) Successful in 12s
ci / build_portal (push) Successful in 5s
ci / build_operator (push) Successful in 5s
ci / build_platform_api (push) Successful in 4s
ci / deploy (push) Successful in 41s
A 'changes' job diffs the push range (github.event.before..sha; falls back to everything on first/force pushes and when this workflow file itself changes) and gates per-app typecheck/test/build jobs. Deploy is asymmetric on purpose: app-only changes roll just the changed Deployments via kubectl set image; manifest changes (fleet/apps/**) apply the kustomization with every app pinned to its live image (or this push's sha) so an apply never resets unchanged apps to :latest. Docs-only pushes run nothing.