Make third-party guideline discovery the default in boost:update - #882
Merged
pushpak1300 merged 2 commits intoJul 21, 2026
Merged
Conversation
New third-party guidelines were only surfaced when running boost:update with an explicit --discover flag, which users are unlikely to reach for. Since discovery already just prompts before including anything, it's safe to run by default so users actually get offered new guidelines. --discover stays accepted so existing usage keeps working, and --no-discover is available to opt out. Closes laravel#879
Member
|
Thanks. |
pushpak1300
approved these changes
Jul 21, 2026
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.
Closes #879
New third-party guidelines are only surfaced when running
boost:update --discover. Few users will realistically use that flag, so in practice new third-party guidelines never get offered on update.Since discovery already just prompts the user before including any newly found guidelines (and is skipped entirely in non-interactive mode), it's safe to run by default.
What changed
boost:updatenow runs discovery by default.--no-discoveradded as an explicit opt-out.--discoverstays accepted so existing usage keeps working.