Open
Conversation
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
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.
What
After a successful
bool create, write the slug and name to.bool/configin the current directory.Why
Previously,
bool createfollowed bybool 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: AddedwriteProjectConfig()call after successful create, matching the behavior ofshipitanddeploy.Testing
Fixes #5