Feat: Add support for explicitly allowing specified directories#41
Merged
Feat: Add support for explicitly allowing specified directories#41
Conversation
This was referenced Mar 22, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Building on PR #38 submitted by @victorujfrog, and subsequent discussion in Issue #39 , this PR adds an
--allow-dirsflag that enables users to specify arbitrary directories to exempt from non-standard directory warnings, orphan file checking, and deep nesting checking.Thank you for filing the original PR, @victorujfrog, and for the discussion that helped refine this implementation! 🎉