Skip to content

chore(gitignore): block data/handover-* + data/spec-* from accidental tracking#334

Merged
mitwilli-create merged 1 commit into
mainfrom
chore/gitignore-handover-and-spec-2026-05-29
May 29, 2026
Merged

chore(gitignore): block data/handover-* + data/spec-* from accidental tracking#334
mitwilli-create merged 1 commit into
mainfrom
chore/gitignore-handover-and-spec-2026-05-29

Conversation

@mitwilli-create
Copy link
Copy Markdown
Owner

Summary

Two glob patterns added to the # Personal data section of .gitignore to block [PERSONAL — DO NOT PUBLISH]-frontmatter docs from accidental tracking via git add -A:

data/handover-*.md
data/spec-*-2026-*.md

5 currently-on-disk files now flip from ?? untracked to !! ignored:

  • data/handover-apply-now-gate-and-popout-grounding-2026-05-29.md
  • data/handover-linkedin-url-canonicalization-2026-05-29.md
  • data/handover-process-all-drain-and-visibility-2026-05-29.md
  • data/handover-triage-eval-quality-gate-2026-05-29.md
  • data/spec-linkedin-url-canonicalization-2026-05-29.md

Why this matters

[PERSONAL — DO NOT PUBLISH] frontmatter is a structural classification — not just a curator note. Without matching .gitignore coverage, a routine git add -A (or a sibling agent's bulk-stage step) can publish the file across the fork boundary in a single keystroke. The two patterns close that surface for every future handover + dated spec doc generated in this workflow.

Aligns with the memory rule feedback_preflight_gitignore_check.md — "Run git check-ignore -v before proposing PR scope or git add; treat [PERSONAL — DO NOT PUBLISH] frontmatter as a structural rule." The pre-flight check is the surfacing mechanism; the .gitignore patterns are the structural backing.

Verification

$ git check-ignore -v data/handover-linkedin-url-canonicalization-2026-05-29.md
.gitignore:8:data/handover-*.md	data/handover-linkedin-url-canonicalization-2026-05-29.md

All 5 files verified — matched by either data/handover-*.md (line 8) or data/spec-*-2026-*.md (line 9).

Scope

  • Single-file PR (.gitignore only)
  • 2 lines added inside the existing # Personal data section
  • Zero code changes
  • Zero behavioral changes — purely a tracking-surface guard

Test plan

  • git check-ignore -v matches all 5 known files
  • Patterns sit inside the existing # Personal data block (line 8-9)
  • No other files affected (.gitignore diff --stat = 1 file changed, 2 insertions(+))
  • CI green (label + ledger-check + analyze + dependency-review + test workflows expected to pass — no code touched)

🤖 Generated with Claude Code

… tracking

Several recently-created docs in data/ carry the `[PERSONAL — DO NOT PUBLISH]`
frontmatter but were untracked, meaning a careless `git add -A` could publish
them across the fork boundary. Two glob patterns close that surface.

Patterns added to the `# Personal data` section:
  data/handover-*.md       — session handover docs (5 currently on disk)
  data/spec-*-2026-*.md    — dated spec docs (1 currently on disk)

Verified via `git check-ignore -v`:
  .gitignore:8:data/handover-*.md	data/handover-linkedin-url-canonicalization-2026-05-29.md
  .gitignore:8:data/handover-*.md	data/handover-apply-now-gate-and-popout-grounding-2026-05-29.md
  .gitignore:8:data/handover-*.md	data/handover-process-all-drain-and-visibility-2026-05-29.md
  .gitignore:8:data/handover-*.md	data/handover-triage-eval-quality-gate-2026-05-29.md
  .gitignore:9:data/spec-*-2026-*.md	data/spec-linkedin-url-canonicalization-2026-05-29.md

Aligns with the memory rule `feedback_preflight_gitignore_check.md` —
`[PERSONAL — DO NOT PUBLISH]` frontmatter is a structural classification
that must be backed by .gitignore coverage, not just a curator note.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@mitwilli-create mitwilli-create merged commit ffc83d8 into main May 29, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant