Skip to content

fix: bool create now writes .bool/config#6

Open
dax5000 wants to merge 1 commit intomainfrom
fix/create-writes-config
Open

fix: bool create now writes .bool/config#6
dax5000 wants to merge 1 commit intomainfrom
fix/create-writes-config

Conversation

@dax5000
Copy link
Collaborator

@dax5000 dax5000 commented Feb 28, 2026

What

After a successful bool create, write the slug and name to .bool/config in the current directory.

Why

Previously, bool create followed by bool deploy . would create a duplicate Bool because deploy didn't know about the one just created. Now subsequent commands (deploy, show, versions, etc.) automatically target the newly created Bool.

Changes

  • src/commands/bools.js: Added writeProjectConfig() call after successful create, matching the behavior of shipit and deploy.

Testing

mkdir /tmp/test && cd /tmp/test
bool create "Test"
cat .bool/config  # ✅ {"slug": "test-xxx", "name": "Test"}
bool deploy .     # ✅ Deploys to test-xxx, not a new Bool

Fixes #5

After a successful 'bool create', write the slug and name to
.bool/config in the current directory. This ensures subsequent
commands (deploy, show, versions, etc.) automatically target the
newly created Bool without requiring the slug explicitly.

Previously, 'bool create' followed by 'bool deploy .' would create
a duplicate Bool because deploy didn't know about the one just created.

Fixes #5
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.

bool create should write .bool/config to link the local directory

1 participant