-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Fix path for local node12 actions #371
Conversation
The changes here are minimal but the PR looks huge because of the node_modules. I can try making the testdata action a compiled version via ncc if that's desired. |
@jromero - i'd rather not have the |
Yup I can compile it as mentioned above. Given that this is more or less a static javascript app the concern of having to update it via compilation seems very minimal. I'll update the PR and squash it. |
bfe6994
to
986a08d
Compare
@cplee updated. Let me know what you think. |
Fixes nektos#185 Signed-off-by: Javier Romero <[email protected]>
986a08d
to
d88bd46
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
awesome @jromero 🎉
…ccessful build is nektos#371, builds after that are failing
* When running on Windows the correct path separator must be used. filePath.join is OS aware, so when we want to use forward slash use path.join instead. on windows docker cp should end with \. when copying a directory when running npm modules we should pass in path with all forward slashes This fixes #331 * When calculating relative folders on Windows for destination path on Linux, we need to change \ for / * Reduce complexity by extracting methods * V1 does not point to a file that does not exist * Looks like something else is the cause of this test breaking. Last successful build is #371, builds after that are failing
This changes makes it so that the proper path is used when executing a local javascript (
node12
) action.Additional minor changes:
make test
to be functional by running expectedgo test
task based on README.mdmake format
to format based on CONTRIBUTING.mdGITHUB_TOKEN
be set only once instead of re-executingcat
per target.expression_tests
to retain previous behaviour (when no file matched) now that apackage-lock.json
file exists intestdata
.Fixes #185