Skip to content

ci: add Gitleaks workflow for secret scanning - #17

Merged
CodeForContribute merged 1 commit into
developfrom
add-gitleaks-workflow
May 4, 2026
Merged

CodeForContribute merged 1 commit into
developfrom
add-gitleaks-workflow

Conversation

@CodeForContribute

Copy link
Copy Markdown
Owner

Summary

  • Adds a Gitleaks GitHub Action that scans the repo for committed secrets.
  • Triggers: push & PR to `main`/`develop`, weekly cron (Mon 06:00 UTC), and manual dispatch.
  • Uses `fetch-depth: 0` so Gitleaks scans the full git history, not just the latest commit.

Why

Catches accidental leaks (API keys, tokens, connection strings) before they hit `main`. The `.env.example` and `.gitignore` are already correctly set up — this adds a safety net for the future.

Test plan

  • Workflow runs successfully on this PR
  • No findings reported (manual scan was clean)
  • Manual `workflow_dispatch` works

Runs on push/PR to main and develop, weekly on schedule, and
manually via workflow_dispatch. Uses fetch-depth: 0 to scan the
full git history.
@vercel

vercel Bot commented May 4, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
flowforge Building Building Preview, Comment May 4, 2026 9:09am

@CodeForContribute
CodeForContribute merged commit 0c2e1cc into develop May 4, 2026
3 of 5 checks passed
@CodeForContribute
CodeForContribute deleted the add-gitleaks-workflow branch May 4, 2026 09:11

This branch had an error being deployed

1 failed deployment
Preview — 003c8209 Deployed May 4, 2026 by vercel[bot]
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