Skip to content

chore(beads): keep bead text out of this public repo - #164

Merged
GeiserX merged 1 commit into
mainfrom
chore/beads-private-tracker
Oct 2, 2026
Merged

GeiserX merged 1 commit into
mainfrom
chore/beads-private-tracker

Conversation

@GeiserX

@GeiserX GeiserX commented Oct 2, 2026 •

Copy link
Copy Markdown
Owner

Bead text was getting into this public repo. Git tracked .beads/interactions.jsonl, the agent interaction log, and sync.remote named this repo, so a bd dolt push would have published the whole tracker under refs/dolt/data.

The fix:

  • sync.remote now names a private Dolt remote, and dolt.auto-commit is on, so every bd write becomes a commit that a push carries.
  • .beads/interactions.jsonl is no longer tracked.
  • .beads/.gitignore now lists issues.jsonl and interactions.jsonl, so neither comes back.

The rest of .beads/ stays committed: config.yaml, README.md, hooks/, metadata.json and .gitignore. I pushed the tracker to the private remote before opening this, and a fresh clone from it matches the local tracker issue for issue.

Summary by CodeRabbit

  • Chores
    • Issue-tracking sync now uses a private remote, and tracker updates are committed automatically.
    • Interaction records are no longer included in the repository.

The tracker's shared copy pointed at this public GitHub repo, and the agent interaction log (.beads/interactions.jsonl) was committed here. Bead text belongs in the Dolt tracker only.

sync.remote now names a private Dolt remote, dolt.auto-commit is on, interactions.jsonl is untracked, and .beads/.gitignore ignores issues.jsonl and interactions.jsonl so neither comes back.
@GeiserX
GeiserX merged commit daa4d2c into main Oct 2, 2026
5 checks passed
@GeiserX
GeiserX deleted the chore/beads-private-tracker branch October 2, 2026 20:38
Repository owner deleted a comment from coderabbitai Bot Oct 5, 2026
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