You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Auto-updating Github Action matrix for node (i.e. ci-config-github-actions) #416
I played around with this a little bit, and since the only re-usable primitive in Github Actions is a step packaged as an "action", the only possible implementation to have an auto-updating matrix is something like this:
1️⃣ Which is suuuuuuuper verbose? Did I miss something? What do people do to solve this issue - do they generate actions or smth from templates? Would we need a CLI or smth to help with that generation? I can't imagine someone copy/pasting that across hundreds of repos in an organization?
2️⃣ It also makes wonder if it's worth maintaining an action, when instead of the uses: nodejs/ci-config-github-actions@master block (5 lines) you could run: npx @pkgjs/node-matrix --gte 10 --policy lts instead?
3️⃣ But if we are to keep the action - should we rename the repo to something that follows the action convetion better, e.g. nodejs/version-matrix-action?
So, in general, looks like this will be somewhat addressed by GH work, and in the meantime we agreed that maybe some node package, which fails things when workflows are out of date might be useful. I'll be doing some related work on wiby side, and will open a new issue if/when I have something that's worth sharing.
fwiw, I’ve made an action ( https://github.com/ljharb/actions/tree/HEAD/node/matrix ) which is reusable, supports semver strings, and is also always up to date. I’ll be using it on all 200-300 of my repos, so hopefully it’ll be reliable :-)
Reacted by Dominykas Blyžė, Owen Buckley and Gary Crye
Activity
thescientist13 commentedon Nov 17, 2020
@dominykas
Looks like something like what you're looking for is on the GitHub roadmap for Q2/2021? github/roadmap#98
dominykas commentedon Nov 17, 2020
Yes, can't wait for workflow partials!
In the meantime sounds like we'll want to build an installable module, so we'll see where that takes us, I guess.
dominykas commentedon Nov 30, 2020
So, in general, looks like this will be somewhat addressed by GH work, and in the meantime we agreed that maybe some node package, which fails things when workflows are out of date might be useful. I'll be doing some related work on wiby side, and will open a new issue if/when I have something that's worth sharing.
Closing this for now.
ljharb commentedon Nov 30, 2020
fwiw, I’ve made an action ( https://github.com/ljharb/actions/tree/HEAD/node/matrix ) which is reusable, supports semver strings, and is also always up to date. I’ll be using it on all 200-300 of my repos, so hopefully it’ll be reliable :-)