What changed, and why it matters
This commit adds a new automated code-quality check called 'tidy' to Bitcoin Core's continuous integration (CI) pipeline. It does not change any Bitcoin software code, user-facing behavior, or network protocol. It only configures GitHub Actions to run an existing cleanup/linting script in a specific Ubuntu environment. There is no security vulnerability here.
No security action needed. Treat as a routine CI/development workflow change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff adds one matrix entry to .github/workflows/ci.yml that runs the existing ./ci/test/00_setup_env_native_tidy.sh environment script on an ubuntu-24.04-based runner with a 120-minute timeout. This is purely CI infrastructure: no source code, build system logic, consensus code, cryptography, or network handling is modified. The change expands test coverage for static-analysis/tidy checks.
Changed components
.github/workflows/ci.ymlInspect captured patch +6 / −0
diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index c59539d3..088b1bd9 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -475,6 +475,12 @@ jobs:
timeout-minutes: 120
file-env: './ci/test/00_setup_env_native_centos.sh'
+ - name: 'tidy'
+ cirrus-runner: 'ghcr.io/cirruslabs/ubuntu-runner-amd64:24.04-md'
+ fallback-runner: 'ubuntu-24.04'
+ timeout-minutes: 120
+ file-env: './ci/test/00_setup_env_native_tidy.sh'
+
steps:
- name: Checkout
uses: actions/checkout@v5
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.