-
Notifications
You must be signed in to change notification settings - Fork 53
add node_modules to git #87
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
base: master
Are you sure you want to change the base?
Conversation
this is described in https://docs.github.com/en/actions/sharing-automations/creating-actions/creating-a-javascript-action#commit-tag-and-push-your-action and not doing that can lead to users not having @actions/core available for example
Interesting, I didn't know that. A question: did you encounter any issue with absence of the "node_modules" directory? |
Yeah. Tried to use the action in a workflow before
Using my branch instead makes that work. |
Oh, that's weird. Would you mind posting your workflow config or the link to the YAML file? |
Sorry, can't do that, private repo. If you're generally up for merging this, it's probably a good idea to automate around this a bit. Like make sure running |
Tried setting up a reproducer here https://github.com/renefritze/msvc-dev-cmd_problem_reproducer |
Yes, I agree. Doing
Yeah, that's what I found weird. I didn't use this action in private repositories before. Since we have only one dependency, I think including "node_modules" does not hurt too much. Lines 29 to 31 in 460a772
You can continue committing new code to this PR, and then wait for @ilammy. |
this is described in https://docs.github.com/en/actions/sharing-automations/creating-actions/creating-a-javascript-action#commit-tag-and-push-your-action and not doing that can lead to users not having @actions/core available for example