Repository navigation
ci: add Change checks - #15
Merged
Merged
Conversation
Runs pinned standard tools on what a change touches: gitleaks on its commits, zizmor on changed workflows, a vulnerability scan of changed lockfiles that fails only when a fixed version exists, and the stack's linters failing only on lines the change added. Build, test and lint stay in the existing CI. Generated from a shared template; edit the template, not this file. Co-Authored-By: Claude Opus 5.5 <[email protected]>
Sulaiman-Dauda
force-pushed
the
change-checks
branch
from
October 21, 2026 08:06
d98833d to
8e3c727
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the Change checks workflow, generated from the shared template.
It runs on every pull request and on pushes to main. gitleaks scans the new commits, zizmor scans any changed workflow, changed lockfiles are scanned for vulnerabilities that have a fixed version, and the linters for this stack fail only on lines the change added. Old findings elsewhere in the repo never fail a PR.
The existing CI keeps build, test and lint. All tools and actions are pinned, the job has read-only permissions and uses no secrets.
Once this is green I will make Change checks a required check on main.
🤖 Generated with Claude Code