-
Notifications
You must be signed in to change notification settings - Fork 1
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
Support parsing node versions from Github Actions #4
Comments
A node version can be defined in any of the
|
Since this is the one I am most interested in, I will post a link to the basic setup I am doing: https://github.com/pkgjs/support/blob/master/.github/workflows/test.yml As you say, this follows the pattern of using If you look for I think this will be brittle, but I am not sure we can do better with the power which GitHub Actions gives. I am going to ping in @bdougieYO from GH to see if maybe someone from their side can give us a better way to do this. @bdougieYO any help (or hook us up with someone who can) would be appreciated! |
I would lean towards what you are describing @wesleytodd. But if I had the bandwidth, I would explore updating the https://github.com/actions/setup-node to provide a $NODE_VERSION env. That way you wouldn't have to guess or need to lean on a deeply nested check. I am not sure if that would get approved and merged, but it would be worth opening up this discussion/issue in that repo. |
This would only be available when the action is running? The tool I'm building is to generate the stats about what people are using in their test setup - so I suspect I'll do what @wesleytodd proposes for now, and I'll see where that takes me after I actually collect some data. |
No description provided.
The text was updated successfully, but these errors were encountered: