Skip to content

sec: add gitleaks CI job scanning full commit history - #331

Open
raaidrushdy wants to merge 3 commits into
mainfrom
sec/gitleaks-ci
Open

sec: add gitleaks CI job scanning full commit history#331
raaidrushdy wants to merge 3 commits into
mainfrom
sec/gitleaks-ci

Conversation

@raaidrushdy

@raaidrushdy raaidrushdy commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

Summary

Adds a CI job that scans the full commit history for secrets using gitleaks on every push/PR to main and staging, plus a weekly scheduled run. Closes the gap identified in the baseline audit (PR #329): pre-commit's detect-secrets only scans staged diffs, so anything already merged into history is invisible to current tooling.

Type of Change

  • CI/CD / infrastructure
  • Security

Affected Components

  • /.github/workflows

Motivation

Covers Planner task 26T2-DEV-RR-003. The baseline audit's manual gitleaks scan found 31 historical findings, including a live GCP service account private key. This automates that check going forward so future exposures are caught on the next push instead of requiring another manual audit to surface them.

Testing Done

  • Tested manually — describe how: Pushed the branch and confirmed the job runs in the Actions tab.

Security Considerations

This job will flag known historical findings (the rotated Fernet key, the GCP key commit) on first run, expected, and confirms the job works correctly rather than indicating a new problem. gitleaks/gitleaks-action is pinned to a commit SHA (e0c47f4, v3.0.0), not a version tag.

Breaking Changes

  • No breaking changes

Rollback Plan

  • Revert commit is sufficient

Checklist

  • Code follows project conventions
  • No secrets, credentials, or tokens committed
  • Relevant documentation updated (if applicable)
  • CI/CD workflows pass on this branch
  • PR is focused on one thing

@raaidrushdy
raaidrushdy requested a review from a team as a code owner August 19, 2026 03:55
@github-actions

Copy link
Copy Markdown
Contributor

Preview Environment

A preview environment can be spun up on demand for this PR.

Action Label Includes
Spin up preview deploy-preview Frontend, backend, database, Redis, OPA, worker
Spin up preview with M365 deploy-preview-m365 Everything above + PowerShell service for Exchange/Teams scan testing
Tear down preview teardown-preview Stops the environment early

The environment will also be torn down automatically when the PR is closed or merged.
Preview URLs will appear in a follow-up comment once the deploy completes (~5–8 min).
M365 scans require real tenant credentials added through the frontend UI.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 8efb612c71

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread .github/workflows/ci.gitleaks.yml Outdated
Comment thread .github/workflows/ci.gitleaks.yml Outdated
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