You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 675886a
Browse filesBrowse the repository at this point in the historyBrowse files
Secret scan (.github/scripts/fork-secret-scan.sh, tests: fork-secret-scan.test.sh)
- The checkout is blob-less, so gitleaks fetched file contents on demand. gitleaks
8.30.1 stops at the first git error (a failed content fetch), logs "0 commits
scanned" and exits 0, and the summary said "No secrets found". The script now
runs gitleaks' own `git log -p -U0 <opts>` first: it fetches every blob the scan
reads and fails the job (exit 2) when a fetch fails. gitleaks then runs with
GIT_NO_LAZY_FETCH=1.
- The job also fails when gitleaks scanned fewer commits than that git log has
commits with a hunk in a file they do not delete (what gitleaks counts; a pure
rename or a clean merge has none, so it can be below rev-list --count).
- New tests: contents unreachable after the clone, gitleaks stopping early, and a
base or head commit that cannot be fetched.
Lint (vp check)
- Formatting of fork-ci-tests.cjs, fork-ci-tests.test.cjs, fork-tests-drift.test.cjs.
- The header comments of fork-ci-tests.cjs and fork-tests-drift.cjs cut to 4 lines
(t3code/no-low-value-comments).
Co-Authored-By: Claude Opus 5.5 <[email protected]>
0 commit comments