config-public

10 Commits 1 Branch 0 Tags

2 Commits

Include renames

Author	SHA1	Message	Date
Lucas WintherandClaude Opus 5	d2c303e346	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 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]>	2026-09-16 04:09:42 +02:00
Lucas WintherandClaude Opus 5	9b9e39e67f	Add the lint configuration and the Makefile ansible-lint at the production profile from the first commit, which is much cheaper than adopting it later. yamllint forbids implicit octal so a file mode cannot silently become an integer, and the Makefile is a thin wrapper so `make check` and CI run byte-identical commands. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>	2026-09-16 03:58:01 +02:00

Author

SHA1

Message

Date

Lucas WintherandClaude Opus 5

d2c303e346

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

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]>

2026-09-16 04:09:42 +02:00

Lucas WintherandClaude Opus 5

9b9e39e67f

Add the lint configuration and the Makefile

ansible-lint at the production profile from the first commit, which is much
cheaper than adopting it later. yamllint forbids implicit octal so a file
mode cannot silently become an integer, and the Makefile is a thin wrapper
so `make check` and CI run byte-identical commands.

Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>

2026-09-16 03:58:01 +02:00