You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Match a Capitalized Secrets Directory in the Runtime-Secrets Check #3842
The runtime-secrets check in spec/audit.py (from #3719, PR #3838) matches a secrets directory's name case-sensitively. A bare directory spelled with a capital, such as Secrets/, breaks the runtimesecrets.naming rule just as secrets/ does, yet no tracked signal naming it is reported. The tree loop's existing .secrets match is case-sensitive in the same way, so a .Secrets/ directory is not judged either.
Expected: a runtime-secrets finding naming the bare directory. Actual: no finding.
Suggested direction
Match the folder name case-insensitively in the .gitignore reader, the reference patterns, and the tree loop, and report a capitalized spelling as drift from .secrets/.
A related line form, from the local review of PR #3838: a .gitignore line with a character class in the folder segment, such as [Ss]ecrets/, makes git ignore a lowercase secrets/. ignored_secrets_folder matches only a segment that is exactly secrets, so a tree holding only that .gitignore reports nothing. A case-insensitive match should cover this form too.
Activity
ptr727 commentedon Nov 3, 2026
A related line form, from the local review of PR #3838: a
.gitignoreline with a character class in the folder segment, such as[Ss]ecrets/, makes git ignore a lowercasesecrets/.ignored_secrets_foldermatches only a segment that is exactlysecrets, so a tree holding only that.gitignorereports nothing. A case-insensitive match should cover this form too.Detect a Bare secrets/ Directory From the Tracked Files That Name It (#…
Fix Adjacent Docs and Review Tails in the Open Pull Request Instead o…