lucasw89/config-public
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix the TOML syntax in the gitleaks config
lint / yamllint + ansible-lint + syntax (push) Successful in 2m26s
Details
lint / shellcheck (push) Successful in 8s
Details
lint / secret scan (push) Successful in 3s
Details

Browse Source 
The title was written with YAML syntax, so gitleaks failed to load the
config before it reached [extend] or [allowlist]:

    FTL unable to load gitleaks config, err: While parsing config: toml:
    expected character =

Verified with the pinned binary the Gitea lint workflow uses (v8.30.1):
`gitleaks detect --source=. --config=.gitleaks.toml --redact --verbose
--no-banner` now scans the working tree and all history and reports no
leaks.

Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
This commit is contained in:
Lucas Winther
2026-09-16 04:09:42 +02:00
co-authored by Claude Opus 5
parent e1f152ec3e
commit d2c303e346
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.gitleaks.toml
+1 -1
View File
@@ -3,7 +3,7 @@
# in .gitlab-ci.yml) over the working tree *and* the history — a secret that was # in .gitlab-ci.yml) over the working tree *and* the history — a secret that was
# committed and then deleted is still a leaked secret, and the only fix is # committed and then deleted is still a leaked secret, and the only fix is
# rotating it. # rotating it.
title: "config repository secret scan" title = "config repository secret scan"
[extend] [extend]
# Start from the upstream rule set rather than reinventing it. # Start from the upstream rule set rather than reinventing it.