Summary
Add a short docs example for GitHub Pages / CRA / static portfolio repos that consume leash-secrets via the GitHub Action only.
Motivation
Portfolio and personal sites often:
- Deploy from
gh-pages or Actions
- Should not vendor
.cursor/rules/leash-secrets.mdc into the site repo
- Need a scan-before-deploy gate
Suggested docs content
- Minimal
secret-scan.yml on push/PR (scan-mode: all, fail-on: critical)
- Deploy workflow with a
needs: secret-scan job
- Note that Cursor/agent rules should be installed via the upstream installer (or global rules), not copied into every consumer repo
- Recommended excludes once #exclude-bug is fixed:
build/**, node_modules/**, dist/**
Acceptance
A docs page or README section with a copy-paste workflow that a GitHub Pages portfolio can adopt without forking leash-secrets content.
Summary
Add a short docs example for GitHub Pages / CRA / static portfolio repos that consume leash-secrets via the GitHub Action only.
Motivation
Portfolio and personal sites often:
gh-pagesor Actions.cursor/rules/leash-secrets.mdcinto the site repoSuggested docs content
secret-scan.ymlon push/PR (scan-mode: all,fail-on: critical)needs: secret-scanjobbuild/**,node_modules/**,dist/**Acceptance
A docs page or README section with a copy-paste workflow that a GitHub Pages portfolio can adopt without forking leash-secrets content.