Skip to content
This repository was archived by the owner on May 10, 2026. It is now read-only.

ci: add gitleaks secret-scan workflow#2

Merged
lx-0 merged 2 commits into
mainfrom
claude/add-secret-scan-ci
Apr 26, 2026
Merged

ci: add gitleaks secret-scan workflow#2
lx-0 merged 2 commits into
mainfrom
claude/add-secret-scan-ci

Conversation

@lx-0
Copy link
Copy Markdown
Member

@lx-0 lx-0 commented Apr 26, 2026

Adds canonical Gitleaks secret-scan CI per consistency-audit follow-up. Template copied byte-identical from agentic-foundation/.github/workflows/secret-scan.yml (de-facto standard across 6 sibling Yesterday-AI repos: agent-services, cloud, openclaw, paperclip-deploy-railway + inlined in agent-calendar/clawrag).

Workflow: Gitleaks (curl-install latest), runs on PR + push to main/master, scans only the PR commit range / push diff (not full history). Permissions read-only, 10min timeout, no GH Marketplace action dep.

No per-repo customization on first pass. Add .gitleaksignore later if false positives appear.

lx-0 added 2 commits April 26, 2026 21:09
Adds canonical Gitleaks secret-scan CI matching the de-facto Yesterday-AI standard (template byte-identical with agentic-foundation, agent-services, cloud, openclaw). Triggers on PR + push to main; scans only the diff (PR commit range or push before..sha), not full history.

No per-repo customization on first pass; add .gitleaksignore later if false positives appear.
Per YyRemy review on llm-gateway#56: github.event.before is the
40-zero null SHA (0000000000000000000000000000000000000000) on the
first push to a new branch. Running 'git log 0000...SHA' fails,
producing a noisy CI error rather than a clean scan.

Fix: branch the push case on whether before is the null SHA. When it
is, scan the full tree (--source . --verbose, no --log-opts). When
it isn't, use the before..sha range as before.

Applied to all 7 of my secret-scan PRs in lockstep so the template
stays uniform across the plugin family.
@lx-0 lx-0 merged commit e185b4e into main Apr 26, 2026
1 check passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant