Add CI/CD Performance
to your pull requests.

P1Zig cache no longer restores anything in preview/release/manual builds · CI/CD Performance

When a preview publish, release tag, or manual artifact build triggers, replacing mlugg/setup-zig with vercel-labs/setup-zig removes the action's Zig global cache, and these workflows have no actions/cache restore/save to compensate, so every run cold-compiles libghostty-vt.

P2DerivedData cache has no restore-keys fallback, so any native source change means cold Xcode build · CI/CD Performance

The cache key hashes all native Apple/Common source files, so every source edit rotates key and stalls zero restore fallback; actions/cache misses each new native change and Xcode rebuilds DerivedData from scratch.

P1sccache replaces Swatinem/rust-cache without a shared backend · CI/CD Performance

When a CI-push run lands on a fresh or different runner, cargo compiles project crates from cold because sccache has no remote backend and its local cache was never saved; the previous Swatinem/rust-cache step that restored from the GitHub Actions cache is gone.

P1Every push to an open PR branch runs the build twice and superseded runs are not cancelled · CI/CD Performance

When a commit is pushed to a branch that heads an open PR, both `push` and `pull_request` (synchronize) fire, so the full macos build runs twice for the same commit; with no concurrency group, prior in-progress runs also keep going.