From d2c303e34636ca3f8cd44a57238121a7742717c0 Mon Sep 17 00:00:00 2001 From: Lucas Winther Date: Wed, 16 Sep 2026 04:09:42 +0200 Subject: [PATCH] Fix the TOML syntax in the gitleaks config 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) --- .gitleaks.toml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.gitleaks.toml b/.gitleaks.toml index 8e207f1..fe7bef4 100644 --- a/.gitleaks.toml +++ b/.gitleaks.toml @@ -3,7 +3,7 @@ # 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 # rotating it. -title: "config repository secret scan" +title = "config repository secret scan" [extend] # Start from the upstream rule set rather than reinventing it.