Repository navigation
Move to maintain-kit v1.0.0 and its secret-scan workflow - #55
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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
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.
What
valuecodes/maintain-kitv1.0.0 (e5bf1d2). The repo was renamed fromvaluecodes/automation, and GitHub does not redirectuses:references, so the scheduled dashboard and updates runs and theworkflow-lintcheck fail until this merges..github/scripts/secrets-scan.shwith the new reusablesecret-scan.yml: gitleaks at the version pinned in maintain-kit, over the full history. The check is nowchecks / secret-scan / gitleaks;pnpm secrets:scanis gone.maintain-kit-dashboard.ymlandmaintain-kit-updates.ymlwith job ids to match, so the runs readmaintain-kit-dashboard / update-issueandmaintain-kit-updates / <kind>.After merging
maintenance-dashboard). The next run opens its replacement undermaintain-kit-dashboard; pin that one. Maintenance dashboard: 🔴 Security alert #50 currently shows a security alert, which the replacement issue will list again if it still applies.maintain-kit/<kind>branches with themaintain-kit-updateslabel. There are no openmaintenance-updates/*PRs or branches to clean up.How to test
pnpm format:check
pnpm lint
pnpm typecheck
pnpm knip
pnpm test
The pre-commit hook ran the new gitleaks line on the commit: no leaks found.
Security review
No security-impacting changes. The scan still runs on every PR and push, now through the pinned reusable workflow; the hook's gitleaks is whatever is installed locally, with CI as the gate.
🤖 Generated with Claude Code