Add a secret-scanning workflow

Runs gitleaks on pushes to main and on pull requests. The settings file
pull_config.sh produces holds API keys in plain text, and .gitignore covers the
default filename, but nothing catches a rename or a key in a test fixture.

.gitleaks.toml allowlists one path: the constant in app/apps/evenhub/even-api.ts
that matches the generic-api-key rule. Scoped by path rather than disabling the
rule, so everything else is still scanned.
This commit is contained in:
JMO committed 2026-09-22 16:28:16 -07:00
1 parent 313ccd86d9
commit c2dbd33e6d
2 files changed
+31

No files matched your search

+22
View File
@@ -0,0 +1,22 @@
name: Secret scan
# Scans for committed secrets on pushes to main and on pull requests.
on:
push:
branches: [main]
pull_request:
permissions:
contents: read
jobs:
gitleaks:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
with:
fetch-depth: 0
- uses: gitleaks/gitleaks-action@v2
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}