-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Description
Problem
bool create creates a Bool on the server and returns the slug, but does not write a .bool/config file in the current directory. This means a subsequent bool deploy . (without explicitly passing the slug) doesn't know about the Bool that was just created — and creates a duplicate Bool instead.
Current behavior
cd my-project
bool create "My Project"
# ✔ Created "My Project" (my-project-abc)
# No .bool/config written
bool deploy .
# Creates a NEW Bool "my-project" (my-project-xyz) — duplicate!Expected behavior
bool create should write .bool/config with the slug (and optionally the name), just like shipit and deploy already do. Then subsequent commands in that directory would automatically target the right Bool.
bool create "My Project"
# ✔ Created "My Project" (my-project-abc)
# .bool/config written with slug: my-project-abc
bool deploy .
# Deploys to my-project-abc ✅Consistency
bool shipit→ writes.bool/config✅bool deploy→ writes.bool/config✅bool create→ does NOT write.bool/config❌
Suggested fix
In src/commands/bools.js, after a successful create, call saveProjectConfig() with the slug and name, similar to how shipit and deploy do it.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels