Closed markdorison closed 3 years ago
@markdorison This is fixed now and I've added a test to the workflow to make sure it doesn't happen again. It'd be great if you could test and confirm that everything's working for you.
@adam7 I have tested and can confirm that I can specify a branch and the action now runs as expected.
Any chance you could cut a new tagged release that includes these changes?
@markdorison Of course, v1.1 is here now 👉 https://github.com/adam7/platformsh-cli-action/releases/tag/v1.1
I tested pointing at v1.1 and it is working as expected. 🎉
When I attempt to use this action, I see the following error:
After doing some initial research, it seems like this is related to the
node_modules
directory not being committed. It looks like it is committed on thereleases/v1
branch but not in the tagged release which is what I am pointing to.