Fix creusot cache by running on push to `master`
What changed, and why it matters
This commit changes the project's automated GitHub workflow so that a verification tool called Creusot also runs whenever code is pushed to the main 'master' branch. The only goal is to make the workflow's build cache work better for pull requests. There is no change to the actual Bitcoin library code, no bug fix, and no security vulnerability being addressed.
No security action needed. This is a CI/CD configuration change to improve cache behavior for the Creusot formal-verification workflow.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The patch adds a push: branches: [master] trigger to .github/workflows/creusot.yml. GitHub Actions caches created during pull_request runs are not shared across PRs; PRs can only restore the cache of the base branch. By running the workflow on pushes to master, a cache is populated on the base branch, which future PRs can then restore. The commit sets permissions: {} (already present) so the workflow has no special repository permissions. No Rust source code is modified.
Changed components
.github/workflows/creusot.ymlInspect captured patch +4 / −0
### .github/workflows/creusot.yml
@@ -1,6 +1,10 @@
name: Creusot
on:
+ # run on push to master required for proper functioning of the cache
+ push:
+ branches:
+ - master
pull_request:
permissions: {}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.