Taras Vozniuk

@Suor: curious what does `userdata: (nil)` stands for? Also seeing bunch of `conj:core_somemodel:id=userdata: (nil)`, is this expected?

Hm, this is strange, It fails at https://github.com/ambientlight/amplify-cli-action/blob/60165d38e083b3e52d7d026e038bdfb08a2fad14/entrypoint.sh#L62 Do you have `amplify/.config/project-config.json` commited in your repo?

The script for now doesn't check whether `amplify/.config` directory exists, I am also not quite sure whether it will run `env pull` without `project-config.json`, please check whether the step runs...

@edvinasbartkus: was unaware of this limitation, will investigate, thanks. Also curious if this alternative might work for you (I haven't attempted anything similar so I have no idea how and...

@edvinasbartkus: sure, I will keep this open until I have more feedback on reimplementing this in `node12`

@danrivett: yes sure, I do see a good point, I have looked into it few month back, reimplementing in node is not complex actually, and this amplify action is quite...

I haven't experienced this myself, thanks a lot for the detailed description, will look into it. > It looks like it might be needed to add smt similar to what...

@juunone: will try to give you an answer this weekend, thanks

> how do i. change build_command ? not only yarn build You can use just a bare bash script inside github actions like, add additional step like: ``` - name:...

> how do i change build_command ? can you can try is to rename your commands and then chaining them, inside `build_command` change `yarn build:dev` to `yarn build_dev && yarn...