[keithwillcode]

What does this PR do?

Optimizes the "Install Dependencies / Yarn install & cache" step in pr.yml by using lookup-only cache checks to avoid downloading ~1.2GB of cache data when caches already exist.

The deps job is primarily for populating the cache when nothing is cached. Previously, even when skipping installs, the cache restore steps would still download all cached data. Now, when skip-install-if-cache-hit: "true" is set:

1. First, run actions/cache/restore@v4 with lookup-only: true to check if caches exist without downloading
2. If all caches hit, skip the entire restore + install flow (no downloads at all)
3. If any cache misses, fall back to normal restore + install + save behavior

This adds a skip-install-if-cache-hit parameter to both the yarn-install and yarn-playwright-install actions (defaulting to "false" for backward compatibility) and enables it only for the deps job in yarn-install.yml.

Mandatory Tasks (DO NOT REMOVE)

• I have self-reviewed the code (A decent size PR without self-review might be rejected).
• I have updated the developer docs in /docs if this PR makes changes that would require a documentation change. N/A - CI workflow change only.
• I confirm automated tests are in place that prove my fix is effective or that my feature works. N/A - CI workflow changes are tested by running CI itself.

How should this be tested?

1. Create a PR with this change
2. On first run (cache miss), the deps job should:
   • Run lookup-only checks (which will miss)
   • Fall back to full cache restore + yarn install + playwright install
3. On subsequent runs (cache hit), the deps job should:
   • Run lookup-only checks (which will hit)
   • Skip ALL cache restore steps and installs (no 1.2GB download)
4. Verify other jobs (type-check, lint, unit-test, etc.) still work correctly as they don't pass the skip flag

Human Review Checklist

• Verify lookup-only steps only run when skip-install-if-cache-hit == 'true'
• Verify restore/install steps are skipped when skip-install-if-cache-hit == 'true' AND cache-hit == 'true'
• Verify the conditional uses yarn-nm-cache-check (the lookup-only step) not yarn-nm-cache (the restore step)
• Confirm default value "false" maintains backward compatibility for other workflows
• Verify same pattern is applied consistently to playwright-install action

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR that start with 'DevinAI' or '@devin'.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

3 Skipped Deployments

Project	Deployment	Review	Updated (UTC)
cal	Ignored		Dec 30, 2025 3:03pm
cal-companion	Ignored	Preview	Dec 30, 2025 3:03pm
cal-eu	Ignored		Dec 30, 2025 3:03pm

[cubic-dev-ai]

2 issues found across 3 files

Prompt for AI agents (all issues)

Check if these issues are valid — if so, understand the root cause of each and fix them.


<file name=".github/actions/yarn-install/action.yml">

<violation number="1" location=".github/actions/yarn-install/action.yml:71">
P2: The lookup-only checks for `yarn-download-cache-check` and `yarn-install-state-cache-check` are performed but their results are never used. Only `yarn-nm-cache-check.outputs.cache-hit` is checked in conditions. Per the PR description (&#39;If all caches hit, skip... If any cache misses, fall back...&#39;), the condition should check all three caches, or the unused lookup-only steps should be removed to avoid wasted CI time.</violation>
</file>

<file name=".github/actions/yarn-playwright-install/action.yml">

<violation number="1" location=".github/actions/yarn-playwright-install/action.yml:31">
P1: The condition breaks backward compatibility. When `skip-install-if-cache-hit` is `&#39;false&#39;` (default), the first operand `inputs.skip-install-if-cache-hit != &#39;true&#39;` is always true, so the install step runs unconditionally—ignoring the cache hit status from `playwright-cache`.

The condition should check `playwright-cache.outputs.cache-hit` in the default case:</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

[cubic-dev-ai]

No issues found across 3 files

[keithwillcode]

merging once https://github.com/calcom/cal.com/actions/runs/20599501603/job/59162093514 completes