-
-
Notifications
You must be signed in to change notification settings - Fork 10
add glob support to extra files #15
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
base: v1
Are you sure you want to change the base?
Conversation
|
Hi, thanks for your PR! I'm pretty finicky about my projects (see this blog post for details), so I rarely merge a PR as-is. For larger PRs, I typically use the GitHub PR review process and provide feedback directly on the code, asking you to make some changes. For smaller PRs, where I just want to tweak some small stuff (like doc wording, comments, code formatting, etc.), I don't do a PR review. Whether or not I do a review, there are two options for merging the PR:
Please let me know which approach you'd prefer. If I don't hear from you before I get around to working on this PR I'll go with option 1. Thanks again for your contribution! |
|
I'm fine with either, though from a purely process-oriented perspective I'd prefer 2. Truth be told, I'm not concerned with having my name on something. You can remove my name from any code added in this PR, as far as I'm concerned. Though I think before you do any work on it, I'd highlight again that there's a big semantic change in here: all I would, and forgive me for giving unsolicited advice here, decide whether that's something I want in this package before I concern myself with the code. :) |
|
Thanks for the heads up. My initial response is just a canned reply I give right away so that when I do get around to looking at the PR, I know what the submitter wants me to do if I plan to merge it. For this one, I need to think about the implications of the change. And if I do decide to merge it, I would bump the major version for the next release. |
|
Sounds good! Let me know if I can support in any way. Cheers! |
e0740a6 to
8c55620
Compare
0c924d9 to
232fa15
Compare
8c55620 to
8d5e97b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR adds glob pattern support to the extra_files input, enabling users to specify file patterns and directories rather than just individual files. This is a breaking change as special characters in file paths will now be interpreted as glob patterns.
- Removes validation that rejected directories in
extra_files - Adds glob pattern expansion with support for recursive patterns (
**) - Converts directory paths to recursive glob patterns (
directory/**)
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| validate-inputs.py | Removes directory validation error, allowing directories as valid extra_files entries |
| make-archive.py | Implements glob expansion logic for extra_files and adds comprehensive test coverage |
| README.md | Documents the new glob pattern functionality and breaking changes |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
All entries in `extra_files` are now interpreted as zglob-style globs. Additionally, directories can be specified and will be expanded to a recursive glob under the directory. File path handling is the same as it has always been. Hidden files are not included in globs and must be spelled out explicitly.
8d5e97b to
41576f9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
This PR adds partial (first issue raised) support for #11.
Caution
This is a breaking change.
extra_filesentries are now interpreted byglob.glob. Files that can be referred to without any escaping in UNIX shells are unaffected, but special characters are now interpreted. Thus, special characters need to be escaped using[]; for example, a literal?is to be expressed as[?].More details on the semantics of entries in
extra_filescan be found here.Changes
extra_files. Directories are removed from the validation and are now considered valid inputs. When a directory is encountered, a suffix of/**is added, so the glob recursively picks up all files inside the directory.glob.glob) is now supported inside theextra_files.**is also supported. Hidden directories are not included. This enables nested patterns such asdir/**/prefix*.ext.I'm not sure this is in line with the direction you want to take this package, it just was the functionality I needed for my project. So, please feel free to reject the PR/propose changes in the way things work.
Thanks for writing this Action!