-
Notifications
You must be signed in to change notification settings - Fork 5
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
Recursive glob #3
Comments
Is what you're asking for the ability to run |
Running this action with |
Got it, just making sure I'm understanding what you're asking. In older versions, this functionality was available (it still says so in the docs) but it clearly no longer works as expected. I'm going to move this issue to https://github.com/get-woke/woke which is the repo where this should be handled. Thanks for reporting! |
👋 Thanks for submitting your first issue! Please be sure to read and follow our Code of Conduct and Contributing guide. ⭐️ Is your org or open source project using |
It does work with woke generally. But woke is just relying on your shell for handling globs. If you turn on I know this for sure because that's how I ended up getting around this. I didn't use this action and just installed woke in my custom action and enabled globstar |
Oh understood, thanks for clarifying. Was too quick in moving the issue to this repo 🙈. Will move back |
If we wanted to add an option to enable globstar for this action, which would be disabled by default (adding something in https://github.com/get-woke/woke-action/blob/main/action.yml and then something like But it might just be worth enabling by default and not even bothering with an input option, since this would be the preferred behavior. Thoughts? |
Is this related to get-woke/woke#211? It would be useful to support glob patterns as input arguments to |
It would be great to have this action support recursive globs so you can check files at any arbitrary level. By default bash has them not enabled. You can enable them by just running
shopt -s globstar
. But given the way all this is packaged up, not something that can be done as far as I can tell outside the action.Adding that option to the script is technically a breaking change, so wanted to file an issue rather than a pr for it. Maybe this is a good option to add?
The text was updated successfully, but these errors were encountered: