We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is your feature request related to a problem? Please describe.
I want to be able to separate builds by architecture or tooling, for example js, go, python, docker.
I don't want to require every engineer to have the same build toolchain.
Describe the solution you'd like
yarn build -c build:*
or
yarn build -c anyScript:*
It should then run every script starting with that prefix.
possibly pair this with an env var, or a .env var to specify which prefix to use when you call yarn build.
.env
yarn build
Describe alternatives you've considered
Currently calling the different ones manually.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Is your feature request related to a problem? Please describe.
I want to be able to separate builds by architecture or tooling, for example js, go, python, docker.
I don't want to require every engineer to have the same build toolchain.
Describe the solution you'd like
yarn build -c build:*
or
yarn build -c anyScript:*
It should then run every script starting with that prefix.
possibly pair this with an env var, or a
.env
var to specify which prefix to use when you callyarn build
.Describe alternatives you've considered
Currently calling the different ones manually.
The text was updated successfully, but these errors were encountered: