Skip to content

Enable gitleaks in console - #1249

Open
punam20 wants to merge 2 commits into
mainfrom
gitleaks
Open

Enable gitleaks in console#1249
punam20 wants to merge 2 commits into
mainfrom
gitleaks

Conversation

@punam20

@punam20 punam20 commented Sep 4, 2026

Copy link
Copy Markdown

Enables gitleaks secret scanning in CI and pre-commit.

@punam20
punam20 requested a review from a team as a code owner September 4, 2026 13:20
@codecov

codecov Bot commented Sep 4, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 56.71%. Comparing base (8156048) to head (1be9e94).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1249   +/-   ##
=======================================
  Coverage   56.71%   56.71%           
=======================================
  Files         149      149           
  Lines       12154    12154           
=======================================
  Hits         6893     6893           
  Misses       5260     5260           
  Partials        1        1           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@punam20
punam20 force-pushed the gitleaks branch 3 times, most recently from 5286c89 to b52f925 Compare September 4, 2026 13:55
punam20 and others added 2 commits September 4, 2026 19:49
Signed-off-by: punam biswal <punam.biswal@intel.com>

@madhavilosetty-intel madhavilosetty-intel left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@punam20 Findings only go to the job log — gitleaks.yml:44 has no --report-path, so nothing is persisted. Trivy, CodeQL and Scorecards in this repo all emit SARIF and upload it. Could we do the same here?

commitlint wants a conventional-commit header, on both the commit and the PR title. Please change to something like ci(gh-actions): add gitleaks secret scanning

Minor one on the description — the gitleaks pre-commit hook was already on main at v8.16.3, so this bumps it to v8.30.1. The CI workflow is the new piece. Might be worth wording it that way?

Comment thread .gitleaksignore
@@ -0,0 +1,24 @@
# Known findings from historical commits that are test-only / example secrets.
# These cannot be scrubbed without rewriting published git history, so they are
# allowlisted by fingerprint instead. See CONTRIBUTING.md before adding new entries.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

.gitleaksignore:3 points to CONTRIBUTING.md, though there's no gitleaks section there yet. Was that meant to come along with this, or should the pointer go?

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.

3 participants