Suppress CI from verbose to progress output
What the developer wrote
Authored by Benalleng
Suppress CI from verbose to progress output
I found progress to still be a dramatic enough length reduction to be
worth it while retaining at least some readability while a job is
running.
What changed, and why it matters
This commit only changes a GitHub Actions CI workflow to reduce how much log output is printed during automated testing. It sets an environment variable named RBMT_LOG_LEVEL to 'progress' so the CI logs are shorter but still readable. There is no change to the actual Bitcoin library code, no security fix, and no vulnerability.
No security action needed. This is a routine CI configuration change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff adds an env block to .github/workflows/rust.yml setting RBMT_LOG_LEVEL: ‘progress’. This is a CI logging/verbosity configuration change only. It does not modify any Rust source, dependencies, build scripts, cryptographic code, network handling, or API surface. No security signals are present.
Changed components
.github/workflows/rust.ymlInspect captured patch +3 / −0
diff --git a/.github/workflows/rust.yml b/.github/workflows/rust.yml
index d6d5b642..5fde8587 100644
--- a/.github/workflows/rust.yml
+++ b/.github/workflows/rust.yml
@@ -10,6 +10,9 @@ name: Continuous integration
permissions: {}
+env:
+ RBMT_LOG_LEVEL: "progress"
+
jobs:
Test:
name: Test - ${{ matrix.toolchain }} toolchain, ${{ matrix.dep }} deps
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.