-
Notifications
You must be signed in to change notification settings - Fork 179
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
No way to exclude specific files #968
Comments
You are correct that the We have had a feature request in our backlog for turning the various $ fossa list-targets
setuptools@path/to/project:requirements.txt
setuptools@path/to/project:dev-requirements.txt
$ fossa analyze --only-target 'setuptools@path/to/project:requirements.txt' I will add a reference to this ticket internally on the tracking ticket for that feature request. |
agree with you @chrisfarnham , I really desperate looking for a way to exclude a specific file, instead of directory only. |
In our Python projects it is a common pattern to have two requirements files:
We explicitly have these two files to separate tools such as sphinx and ansible which have licenses that allow development use but we do not want to link within our code or "distribute" with our products.
I can't find a way to have the FOSSA configuration ignore an individual file. If I specify paths.exclude: dev-requirements.txt in .fossa.yml or other mechanisms it is ignored. I believe these configs only work at a directory level.
At this time I'm forced to delete the dev-requirements.txt from the root directory before fossa analyze which is undesirable.
Can we allow excludes at a file level to support this use case?
I believe that having requirements files for each environment (dev,test,prod) is fairly common. Licensing implications is one reason why.
The text was updated successfully, but these errors were encountered: