Prevent boost:update from failing when there is nothing to update - #907
Merged
Conversation
Member
|
Thanks |
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.
Currently
boost:updateneeds configured agents before it checks whether there is anything to update, so an MCP-only setup (php artisan boost:install --mcp) getsPlease set up Boost with [php artisan boost:install] first.and a non-zero exit code.This PR reorders the checks in
handle()so that when guidelines or skills aren't configured the command exits successfully before requiring the agents part.Example run that shows the current behaviour in a new project that this PR (seems to!) fix: