Replies: 2 comments
-
|
Added to Turborepo 2.0 in this PR: #8142 |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Hi, we're currently in the process of deciding how we want to better signal possible typos in filters without adding another flag. Will communicate back on this issue once we come to a decision. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Which project is this feature idea for?
Turborepo
Describe the feature you'd like to request
Hi everyone,
The specific scenario, for my case, is for GitHub actions, I have some workflows that run tests for different workspaces, and the problem is when there are some misspelled workspaces the execution silently ignores them and succeeds even though it didn't find any workspaces.
Describe the solution you'd like
If you run:
instead of
yarn turbo run test --filter=graphql-apiit should abort the execution maybe with a flag
--strictor something like that.Describe alternatives you've considered
The alternative that I considered is to save the output of the command and check its content to see if it matches:
Running test in 0 packagesBeta Was this translation helpful? Give feedback.
All reactions