Skip to content
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

Warn when --exclude///> using exclude does not actually exclude any files from the project #3387

Open
Gedochao opened this issue Dec 20, 2024 · 0 comments
Labels
--exclude Issues tied with the excluding inputs. enhancement New feature or request UX

Comments

@Gedochao
Copy link
Contributor

Version(s)
1.5.4 and 4ab3227

Describe the issue
When declaring a path or pattern in --exclude///> using exclude, I'd like a warning if no sources were actually caught by the pattern I declared. This would make it easier to catch when my exclusion actually works.
Additionally, I'd like some debug logs under -v -v -v telling me which files were, in fact, excluded.

@Gedochao Gedochao added enhancement New feature or request UX --exclude Issues tied with the excluding inputs. labels Dec 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
--exclude Issues tied with the excluding inputs. enhancement New feature or request UX
Projects
None yet
Development

No branches or pull requests

1 participant