Repository navigation
Conversation
bd 1.3.0 keeps issues in a Dolt server rather than SQLite and JSONL. metadata.json points at the server, .envrc loads the password from the untracked .env.local, and the gitignores cover the files bd now drops.
Playwright test results
Details
Failed testssmoke.spec.ts › E2E smoke test with local services › frontend loads without JavaScript errors Skipped testspop-out.spec.ts › Popping Out › user can pop out and cancel to return to normal schedule |
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
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.
bd 1.3.0 keeps issues in a Dolt server instead of SQLite with a JSONL export. This points
.beads/metadata.jsonat that server, adds an.envrcthat loads the server password from the untracked.env.local, and ignores the files bd now writes, including the gate lock at the repo root..beads/issues.jsonlstays as the record of what was imported.