Skip to content

Remove tracked Beads metadata#392

Open
MaxGhenis wants to merge 2 commits intomainfrom
codex/remove-beads-metadata
Open

Remove tracked Beads metadata#392
MaxGhenis wants to merge 2 commits intomainfrom
codex/remove-beads-metadata

Conversation

@MaxGhenis
Copy link
Copy Markdown
Contributor

Summary

  • remove tracked .beads metadata from the repository
  • keep GitHub issues/PRs as the source of truth instead of repo-local Beads state

Closes #391.

Tests

  • Not run; metadata-only removal.

@MaxGhenis MaxGhenis marked this pull request as ready for review May 4, 2026 16:48
@vahid-ahmadi
Copy link
Copy Markdown
Collaborator

Suggestions / things to flag

  • Local hooks aren't covered by this PR. Remove tracked Beads metadata #391 mentions "local Beads hooks can block normal commits." Anyone who installed Beads locally will still have .git/hooks/* entries and a daemon — the PR description should probably mention that contributors who previously ran bd init may need to bd uninstall (or just delete the local hook scripts) to fully stop the sync attempts. Worth a one-line note in the PR body.
  • Stale clones. After merge, anyone with the directory locally will keep an untracked .beads/ folder containing *.db, daemon.lock, etc. Not a blocker, but a heads-up in the merge commit / release notes is friendly.
  • PR body says "Tests: Not run" — appropriate here; this is metadata-only and CI's existing test suite is sufficient validation.

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.

Remove tracked Beads metadata

2 participants