feat: add recursive option, defaults to true #11
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi John et al.,
My use case is that I have a fairly high number of starters all within one directory in a monorepo. I don't want a single change to one starter to trigger the publish workflow across all starters. So I modified this to add a "recursive" option. This probably isn't a perfect or final API, but more an idea. This is also my first time writing bash scripting, so I wouldn't merge this. Moreso it is a proof of concept.
The recursive option is set to default to true, so that means the action continues to function as-is for current users. However when set to false the folder specified is exact and no recursive searching is completed. For example if the folder is specified as "starters/gatsby-starter-awesome" then it will only look in that one specific folder and not recursively inside of it.
I hope that makes sense, I would be happy to explain or discuss more if needed.