fix: show error when --tasks flag doesn't match any tasks in build command#10027
Merged
Conversation
…mmand Previously, when running `bit build --tasks <non-existent-task>`, it would show a success message like "Running build pipeline using 6 environment(s), total 0 tasks. Succeeded in 10s" even though no tasks matched the filter. Now it properly throws an error indicating which tasks were not found and lists all available tasks to help users correct their command.
luvkapur
approved these changes
Oct 3, 2025
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
2 participants
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.
Fixes an issue where
bit build --tasks <non-existent-task>would show a misleading success message instead of an error.Before:
After:
Changes:
calculatePipelineOrder()to check if task filtering resulted in an empty queue