Implement blacklisting and whitelisting #176
Merged
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.
Blacklisting and whitelisting can now be done on the export page. Blacklists are applied first, and then whitelists. This means you can blacklist a directory but whitelist a file within that directory. In the GUI, patterns are separated by lines. In command line mode, patterns are separated using commas (
,
).To blacklist/whitelist a directory or file called "project_files" recursively, put this into the new blacklist/whitelist field:
You can also exclude a directory in the root of your project directory like so:
There is also support for simple patterns. To match
files
andfiled
, you can do:In the GUI, a file tree on the right of the new fields shows which files will be included in the build. This will show all files including hidden ones if they are allowed with the blacklist/whitelist patterns.