Greptile Summary

Replaces always() with !cancelled() on the final aggregator job so it respects the workflow's cancel-in-progress: true concurrency setting. The fix correctly avoids spinning up a runner — and producing error annotations — on superseded commits while still catching upstream failures and skips.

Confidence Score: 5/5

Safe to merge — minimal, correct one-line fix with no functional regressions on normal CI paths.

The change is a single condition swap on a non-critical aggregator job. Both success and failure cases are handled identically to before; only cancelled workflows behave differently (correctly skipping the job). No logic, data, or security concerns.

No files require special attention.

Important Files Changed

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[New commit pushed] --> B{cancel-in-progress}
    B -- "supersedes previous run" --> C[Previous workflow cancelled]
    B -- "no active run" --> D[Jobs run normally]
    C --> E{final job condition}
    D --> F[Jobs complete\nsuccess / failure / skipped]
    F --> G{final job condition}
    E -- "always() (old)" --> H[final runs anyway\nwastes runner, confusing annotations]
    E -- "!cancelled() (new)" --> I[final skipped ✓]
    G -- "!cancelled() (new)" --> J{Any failure/skipped/cancelled?}
    J -- yes --> K[exit 1 — CI fails ✓]
    J -- no --> L[exit 0 — CI passes ✓]

_{Reviews (1): Last reviewed commit: "chore(ci): use !cancelled() instead of a..." | Re-trigger Greptile}