What changed, and why it matters
This commit is a routine CI (Continuous Integration) configuration change for the Bitcoin Core repository. It adds a single environment variable that tells the project's GitHub Actions workflow to use faster Cirrus-provided runners and caching when running tests on the main bitcoin/bitcoin repository or pull requests against it. There is no code change affecting the Bitcoin software itself, wallets, transactions, networking, or cryptography.
No security action required. Review as normal infrastructure configuration change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies .github/workflows/ci.yml, adding REPO_USE_CIRRUS_RUNNERS: ‘bitcoin/bitcoin’ to the env section. This variable is consumed by the CI scripts to decide whether to schedule jobs on Cirrus runners (with associated caching) versus default GitHub Actions runners. It is purely an infrastructure/CI optimization and does not alter build logic, source code, secrets handling, or permissions.
Changed components
.github/workflows/ci.ymlInspect captured patch +1 / −0
diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index 03d11536..bd9c0b64 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -20,6 +20,7 @@ concurrency:
env:
CI_FAILFAST_TEST_LEAVE_DANGLING: 1 # GHA does not care about dangling processes and setting this variable avoids killing the CI script itself on error
MAKEJOBS: '-j10'
+ REPO_USE_CIRRUS_RUNNERS: 'bitcoin/bitcoin' # Use cirrus runners and cache for this repo, instead of falling back to the slow GHA runners
defaults:
run:
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.