Skip to content

ci: optimize workflow caching and checkouts#29874

Merged
Qbandev merged 3 commits into
mainfrom
feat/mcwp-592-ci-cache-shallow-clone
May 8, 2026
Merged

ci: optimize workflow caching and checkouts#29874
Qbandev merged 3 commits into
mainfrom
feat/mcwp-592-ci-cache-shallow-clone

Conversation

@Qbandev

@Qbandev Qbandev commented May 7, 2026

Copy link
Copy Markdown
Contributor

Description

Optimizes selected CI workflows by using Yarn cache support for the EAS update dependency install and avoiding full-history checkouts where the jobs do not need repository history.

This leaves history-sensitive workflows unchanged, including feature-flag registry, merge-base, tag, branch-sync, and SonarCloud paths.

Validation:

  • Parsed the changed workflow YAML files locally.
  • Ran the requested workflow grep for fetch-depth: 0, actions/setup-node, yarn install --immutable, and selected git commands.
  • Ran git diff --check.
  • Ran actionlint on changed workflows, with pre-existing actions/*@v3 and disabled-job warnings ignored.
  • Ran a diff-scoped Codex Security scan: no findings.

Changelog

CHANGELOG entry: null

Related issues

Refs: MCWP-592

Manual testing steps

N/A - workflow-only CI change.

Screenshots/Recordings

Before

N/A

After

N/A

Pre-merge author checklist

Performance checks (if applicable)

  • I've tested on Android
    • Ideally on a mid-range device; emulator is acceptable
  • I've tested with a power user scenario
    • Use these power-user SRPs to import wallets with many accounts and tokens
  • I've instrumented key operations with Sentry traces for production performance metrics

For performance guidelines and tooling, see the Performance Guide.

Pre-merge reviewer checklist

  • I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
  • I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

@Qbandev Qbandev self-assigned this May 7, 2026
@metamaskbotv2 metamaskbotv2 Bot added the team-dev-ops DevOps team label May 7, 2026
@github-actions github-actions Bot added the pr-not-ready-for-e2e Skip E2E and block merging. Remove this label once the PR is ready to run the E2E tests. label May 7, 2026
@github-actions

github-actions Bot commented May 7, 2026

Copy link
Copy Markdown
Contributor

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

@Qbandev Qbandev added no-changelog no-changelog Indicates no external facing user changes, therefore no changelog documentation needed size-XS labels May 7, 2026
@github-actions github-actions Bot added size-S and removed size-XS labels May 7, 2026
@Qbandev Qbandev force-pushed the feat/mcwp-592-ci-cache-shallow-clone branch from 6004b09 to 27a01d3 Compare May 7, 2026 16:04
@Qbandev Qbandev removed the pr-not-ready-for-e2e Skip E2E and block merging. Remove this label once the PR is ready to run the E2E tests. label May 8, 2026
@Qbandev Qbandev marked this pull request as ready for review May 8, 2026 10:45
@Qbandev Qbandev requested review from a team as code owners May 8, 2026 10:45
@Qbandev Qbandev added this pull request to the merge queue May 8, 2026
@github-merge-queue github-merge-queue Bot removed this pull request from the merge queue due to failed status checks May 8, 2026
@Qbandev Qbandev added this pull request to the merge queue May 8, 2026
@github-merge-queue github-merge-queue Bot removed this pull request from the merge queue due to failed status checks May 8, 2026
@github-actions

github-actions Bot commented May 8, 2026

Copy link
Copy Markdown
Contributor

🔍 Smart E2E Test Selection

  • Selected E2E tags: None (no tests recommended)
  • Selected Performance tags: None (no tests recommended)
  • Risk Level: low
  • AI Confidence: 97%
click to see 🤖 AI reasoning details

E2E Test Selection:
All 4 changed files are GitHub Actions workflow files with purely CI/build infrastructure optimizations:

  1. build.yml: Changes fetch-depth: 0fetch-depth: 1 in checkout steps (shallow clone optimization), plus adds explicit fetch-depth: 1 to a step that previously had no setting.
  2. create-build-branch.yml: Changes fetch-depth: 0fetch-depth: 1.
  3. push-eas-update.yml: Changes fetch-depth: 0fetch-depth: 1 in multiple checkout steps, plus adds cache: 'yarn' to Node.js setup for build caching.
  4. upload-to-testflight.yml: Changes fetch-depth: 0fetch-depth: 1.

These changes:

  • Only affect how git history is fetched during CI builds (shallow vs full clone) — a common optimization to speed up CI pipelines
  • Do not modify any application source code, test code, or test infrastructure
  • Do not affect what gets built, how it's built, or what tests run
  • Do not impact any user-facing functionality or app behavior
  • The cache: 'yarn' addition is a minor CI caching improvement with no functional impact

No E2E tests are needed as there are no application code changes to validate.

Performance Test Selection:
These are purely CI workflow optimizations (shallow git clone settings and yarn caching). No application code, rendering logic, state management, or performance-sensitive paths were changed. No performance tests are warranted.

View GitHub Actions results

@Qbandev Qbandev added the release-7.78.0 Issue or pull request that will be included in release 7.78.0 label May 8, 2026
@Qbandev Qbandev enabled auto-merge May 8, 2026 13:58
@sonarqubecloud

sonarqubecloud Bot commented May 8, 2026

Copy link
Copy Markdown

@Qbandev Qbandev added this pull request to the merge queue May 8, 2026
Merged via the queue into main with commit 4b4292d May 8, 2026
58 of 60 checks passed
@Qbandev Qbandev deleted the feat/mcwp-592-ci-cache-shallow-clone branch May 8, 2026 14:28
@github-actions github-actions Bot locked and limited conversation to collaborators May 8, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

no-changelog no-changelog Indicates no external facing user changes, therefore no changelog documentation needed release-7.78.0 Issue or pull request that will be included in release 7.78.0 size-S team-dev-ops DevOps team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants