Skip to content

decay-refactor: pass GITHUB_TOKEN to gitleaks-action for PR scans - #50

Open
jayelbotvibe-web wants to merge 3 commits into
mainfrom
decay-refactor/ci-gitleaks-token
Open

decay-refactor: pass GITHUB_TOKEN to gitleaks-action for PR scans#50
jayelbotvibe-web wants to merge 3 commits into
mainfrom
decay-refactor/ci-gitleaks-token

Conversation

@jayelbotvibe-web

Copy link
Copy Markdown
Owner

Problem

CI fails on every PR with:

🛑 GITHUB_TOKEN is now required to scan pull requests.

Fix

Pass GITHUB_TOKEN env var to gitleaks/gitleaks-action@v2 in .github/workflows/ci.yml.

Affects

PR #49 (decay/00-recon) and all future PRs — the CI workflow runs from the base branch's config.

@jayelbotvibe-web
jayelbotvibe-web force-pushed the decay-refactor/ci-gitleaks-token branch from 49bd9ef to d8f16a1 Compare July 10, 2026 05:57
jayelbotvibe-web and others added 2 commits July 19, 2026 19:13
…ab creds

The gitleaks-action@v2 requires GITHUB_TOKEN for PR scans; even with the token
it would then fail on real findings in scripts/verify-lab.sh. Replace the
action with a self-contained gitleaks CLI scan (no token, no API) and remove
the secrets it flags:

- verify-lab.sh: drop hardcoded `admin:SecretPassword`; source indexer and API
  credentials from the environment and pass them via a single variable so no
  `user:pass` literal remains for the curl-auth-user rule to match.
- ci.yml: download pinned gitleaks 8.28.0 and run `gitleaks dir` against the
  repo with .gitleaks.toml.

Verified locally: `gitleaks dir` reports no leaks; go build/test green.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant