Add profile parameter to specifiy include/exclude in verbatim #51
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
If there are already sources for rsync-style include/exclude specifications, it is hard to adapt them to the plain array style of the `include_filelist` and `exclude_filelist` parameters. This commit adds the ability to set the content verbatim, while forcing the exclusive use of this feature. It is meant as a power user feature for cases, where the include/exclude specification is of a more complex nature.
|
Nice! |
|
Released as 4.8.0 to the forge, thanks for the contribution. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
If there are already sources for rsync-style include/exclude specifications, it is hard to adapt them to the plain array style of the
include_filelistandexclude_filelistparameters.This commit adds the ability to set the content verbatim, while forcing the exclusive use of this feature. It is meant as a power user feature for cases, where the include/exclude specification is of a more complex nature.