chore(reports): track reports/ by default; add gitignored reports/private/ - #25
Merged
Merged
Conversation
…vate/
The blanket `reports/` gitignore was removed — a secret-pattern audit (2026-06-26)
of all 24 files found nothing sensitive (no keys/tokens/credentials/connection
strings/PII), and most reports were already tracked, making the rule mostly
redundant. Engineering reports, the risk register, and post-mortems are now
tracked by default.
Secret-prone / non-public material now goes under `reports/private/`, which stays
gitignored (only its README is tracked, to document the convention):
reports/private/*
!reports/private/README.md
Also commits reports/phase3_test_coverage_audit.md (the one previously-hidden,
audited-clean report surfaced by un-ignoring reports/).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Make
reports/tracked by default and move secret-prone material to a dedicated ignored subfolder.Why
The blanket
reports/gitignore was over-broad. A secret-pattern audit (2026-06-26) of all 24 files found nothing sensitive — no API keys, tokens, credentials, connection strings, auth headers, emails, public IPs, or base64 key-blobs (all files are engineering reports / post-mortems / plans / the risk register). Most reports were already tracked anyway, so the rule was largely redundant.Change
.gitignore: drop the blanketreports/ignore; add a narrow rule so only a private subfolder stays ignored:reports/private/README.md: documents that this folder is gitignored and is the home for credential/PII/non-public material.reports/phase3_test_coverage_audit.md: the single previously-hidden (audited-clean) report surfaced by un-ignoringreports/, now tracked.Verified
reports/private/→ ignored ✅reports/private/README.md→ tracked ✅No code change.
🤖 Generated with Claude Code