chore: gitignore .beads and the proto coder's per-session scratch#37
Merged
Conversation
Found live: a dogfood run pointed a team's project_board.repo directly at this repo's own dev checkout, and _beads_init's `br init` + the coder's commit-everything habit swept an empty .beads/ (per-instance board state) into a local commit -- never pushed, caught before it reached origin. .beads is instance-local runtime state, not something the plugin's own source repo should ever track (projectBoard-plugin's own .gitignore already draws this line). Add both that and the proto coder's known per-session scratch paths so this can't happen again to any future checkout used as a team's repo. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
👀 Quinn is reviewing — verdict (PASS / WARN / FAIL) + findings to follow. |
![protoquinn[bot]](https://avatars.githubusercontent.com/in/3282126?s=60&v=4){kind=small}
There was a problem hiding this comment.
QA Audit — PR #37 | chore: gitignore .beads and the proto coder's per-session scratch
VERDICT: PASS (tentative — CI still running, re-dispatch will confirm)
CI Status
- test: in_progress ⏳
Diff Review
.gitignoreonly: adds.beads/,.beads-demo/(per-instance board state) and proto agent scratch paths (.proto/memory/,.proto/session-notes.md,.proto/repo-map-cache.json)- Well-scoped: excludes
.proto/evolve/deliberately — protoCLI-managed skills stay versioned - Inline comments explain the "why" for each block — good hygiene
Observations
- No findings. Clean, docs-only
.gitignoreaddition. Mirrors the established convention from projectBoard-plugin.
— Quinn, QA Engineer
|
Submitted COMMENT review on #37. CI still running — formal PASS/FAIL will land on re-dispatch once |
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.
Found live during dogfooding: a team's `project_board.repo` pointed directly at this repo's own dev checkout, and `_beads_init`'s `br init` (plus the coder's commit-everything habit) swept an empty `.beads/` — per-instance board state — into a local commit. Never pushed, caught before it reached origin.
`.beads` is instance-local runtime state, not something the plugin's own source repo should ever track — `projectBoard-plugin`'s own `.gitignore` already draws this line (`.beads/`, `.beads-demo/`). Mirror it here, and add the `proto` coding agent's known per-session scratch paths (`_exclude_proto_scratch`'s own list) so a future checkout used as a team's repo can't hit this again.
Docs-only change (a `.gitignore` addition); gate green, no code touched.
🤖 Generated with Claude Code