-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
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
Bring back build_command support #11
Comments
@juunone: will try to give you an answer this weekend, thanks |
@ambientlight thanks for answering |
You can use just a bare bash script inside github actions like, add additional step like:
Hm, how did you configure here? |
i use like this. |
can you can try is to rename your commands and then chaining them, inside |
package.json
yml
project-config.json
sorry for my question detail. explain more detail to you i think build_command is not overwrite in project-config.json BuildCommand. |
@juunone: If I understood your setup, you want to trigger conditional build command, that is |
is amplify-cli-action |
@juunone: I am sorry for the confusion,
So, to reiterate, |
@ambientlight i understand it. thanks than you know want i want help things.
how do i build with multiple command? |
@juunone: you need to override I think overriding project-config.json |
@ambientlight yes please~! thanks for my long question for answer and i will wait for feature will bring back to soon |
hi i have question for use this amplify action
i change to build command to
build_command: 'yarn build:dev'
like this.i have multiple build scripts in package.json
it has each have other build scripts
and i want to publish with yarn:dev script but when i try action
it only use yarn build..
how do i. change build_command ? not only yarn build
second i try to
project_dir
amplify
andamplify_rnd
i have configure and publish with
project_dir: 'amplify_rnd'
but it only look
amplify
is am i wrong with use project_dir?
amplfiy_rnd have proejct-config.json and "BuildCommand": "yarn build:rnd"
i will wait for answer
thanks.
The text was updated successfully, but these errors were encountered: