Skip to content

build: skip sscache action on non-main branches#61790

Open
joyeecheung wants to merge 3 commits intonodejs:mainfrom
joyeecheung:skip-non-main
Open

build: skip sscache action on non-main branches#61790
joyeecheung wants to merge 3 commits intonodejs:mainfrom
joyeecheung:skip-non-main

Conversation

@joyeecheung
Copy link
Member

@joyeecheung joyeecheung commented Feb 12, 2026

To reduce cache thrashing.

From a look at the action results, PRs targeting non-main generally don't have a good cache hit rate anyway, so it seems better to just keep it to main where the majority of the volume is:

https://github.com/nodejs/node/actions/runs/21866462915
https://github.com/nodejs/node/actions/runs/21866461713

Refs: #61436

@nodejs-github-bot
Copy link
Collaborator

Review requested:

  • @nodejs/actions

@nodejs-github-bot nodejs-github-bot added the meta Issues and PRs related to the general management of the project. label Feb 12, 2026
@codecov
Copy link

codecov bot commented Feb 12, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 88.85%. Comparing base (4a13a62) to head (ce65f4f).
⚠️ Report is 24 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #61790      +/-   ##
==========================================
- Coverage   89.76%   88.85%   -0.91%     
==========================================
  Files         675      675              
  Lines      204674   204806     +132     
  Branches    39330    39262      -68     
==========================================
- Hits       183716   181971    -1745     
- Misses      13235    15050    +1815     
- Partials     7723     7785      +62     

see 115 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@targos targos added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Feb 12, 2026
@aduh95 aduh95 added lts-watch-v20.x PRs that may need to be released in v20.x lts-watch-v22.x PRs that may need to be released in v22.x labels Feb 13, 2026
Co-authored-by: Antoine du Hamel <duhamelantoine1995@gmail.com>
Comment on lines +40 to +41
CC: ${{ (github.base_ref == 'main' || github.ref_name == 'main') && 'sccache clang-19' || 'clang-19' }}
CXX: ${{ (github.base_ref == 'main' || github.ref_name == 'main') && 'sccache clang++-19' || 'clang++-19' }}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we apply the same here, to avoid repetition

Co-authored-by: Antoine du Hamel <duhamelantoine1995@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author ready PRs that have at least one approval, no pending requests for changes, and a CI started. lts-watch-v20.x PRs that may need to be released in v20.x lts-watch-v22.x PRs that may need to be released in v22.x meta Issues and PRs related to the general management of the project.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants

Comments