-
Notifications
You must be signed in to change notification settings - Fork 214
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
Add globbing support #1524
Add globbing support #1524
Conversation
I can wait to see this merged. Interesting how the globbing was silently removed on each major version... |
bfb40d9
to
f0bf605
Compare
I tried deduping deps, but it only found duplicate devdeps, so the build didn't get any smaller 😢 |
It might make sense to use @actions/glob, like |
I hadn't heard of that, but yes, it looks like a better alternative. |
That seems to be a known issue: actions/toolkit#1560, actions/toolkit#1697. I suppose the one benefit of using the "official" package is that it's likely to already be installed. However, I don't feel strongly about it, and we can wait to see what the maintainers suggest. 🙂 |
Actions are pre-bundled, it'd get reinstalled.
They're currently doing a rewrite in bash, see #1591 (comment). |
Oh, that's a strange thing to do. 😕
I saw this, but I misread it as being related to the eslint setup. 🙂 We've actually just switched to using the default file search mode where you don't specify the files. Probably not the most efficient, but it works for now. |
Yeah, actions are weird.
That's what I've been doing as well, works well enough for now. |
Closing due to the v5 refactor; +1 #1582 instead. |
Fixes #770 for real (and fixes #1582).
Personally, I think this change belongs in the cli, but I decided that rewriting the argument parsing there was a much larger endeavor than this.
Tests are failing because it now globs the files, but they don't actually exist. I suppose we need fixtures then? Shouldn't be breaking in practice though.