You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
feat: support ** recursive glob patterns in --exclude #15
--exclude currently uses filepath.Match (shell glob), which does not support ** recursive matching. This means you cannot exclude nested directories like vendor/, node_modules/, or dist/ without specifying exact paths.
# This does NOT work today — no recursive match
dupehound scan --exclude "vendor/**" --exclude "node_modules/**"
# Workaround is painful and incomplete
dupehound scan --exclude "vendor/*" --exclude "node_modules/*"
For real-world codebases (Go modules, JS monorepos, generated code dirs), this is a blocking gap for adopting dupehound in CI.
Proposed behavior
Support ** in --exclude patterns using doublestar or equivalent:
# Exclude entire directory trees
dupehound scan --exclude "vendor/**" --exclude "node_modules/**"
# Exclude generated files anywhere in the tree
dupehound scan --exclude "**/*.pb.go" --exclude "**/*_generated.go"
# Exclude a nested test fixtures dir
dupehound scan --exclude "**/testdata/**"
Same syntax should apply to exclude: in .dupehound.yml:
Activity
feat: extend domain types and CLI flags for new features (#15-#23)
feat(#16,#15,#17): binary skip, ** glob excludes, and --include filter
fix(reporter): cover gaps in #15-#23 and de-noise text/markdown output
docs: add EXAMPLES.md cookbook and link from README
feat(#15-#23): nine enhancements + diff-aware --since rewrite + safet…