Fix beads git tracking after bd to br migration#73
Merged
Conversation
5 issues for known Windows test failures not addressed in PR #72: - bd-1d3e: CRLF failures in quarto-doctemplate (8 tests) - bd-18wn: File-locking failures in quarto-hub (2 tests) - bd-2w80: CSL manifest failure after rebase - bd-2rbk: Pampa test skip behavior without Pandoc - bd-238o: Port pampa Windows fixes from quarto-markdown
Add .beads/.gitignore matching br init defaults and remove beads rules from root .gitignore (let br own its ignore list). Untrack files that should be local-only: .br_history/, beads.db, last-touched, .local_version, deletions.jsonl.migrated. Comment out unused sync-branch config in config.yaml. Tracked files remaining: issues.jsonl, config.yaml, metadata.json, README.md, .gitignore.
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
2 participants
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.
This repo was originally set up with steveyegge/beads (
bd), which auto-manages.beads/.gitignoreat runtime —bd initcreates it,bd doctor --fixregenerates it, and sincebdrewrites it on the fly, the root.gitignoreexcludes it from tracking (line 17:.beads/.gitignore).After switching to Dicklesworthstone/beads_rust (
br), this breaks:brwrites.beads/.gitignoreonce duringbr initand never touches it again. There is nobr doctorthat auto-repairs it. With the root.gitignorestill blocking it, the file is invisible to git and the patterns inside (like.br_history/) have no effect.The result is that local-only artifacts get committed on every
git add .beads/:.br_history/snapshots (~545KB full copies ofissues.jsonlafter every mutation), the SQLite database, temp files, and migration artifacts.Changes
Add
.beads/.gitignorematchingbr initdefaults. Ignores*.db,.br_history/, lock files, merge artifacts, and other local-only files.Replace
bd-era beads rules in root.gitignorewith a one-line comment pointing to.beads/.gitignore.Untrack files that should be local-only:
.br_history/,last-touched,.local_version,deletions.jsonl.migrated.Comment out
sync-branch: "beads-sync"inconfig.yaml— abdfeature not used bybr.Add 5 beads issues for known Windows test failures discovered during Add Windows development support and contributor onboarding #72 (CRLF in quarto-doctemplate, file-locking in quarto-hub, CSL manifest, pampa test skips, pampa Windows ports).
After this change, only portable files remain tracked:
issues.jsonl,config.yaml,metadata.json,README.md,.gitignore.