-
Notifications
You must be signed in to change notification settings - Fork 312
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
Make recursive cloning (e.g. of Git submodules) configurable #6697
Comments
@dgutson Can you explain where exactly you need this option? Do you want an option for the download command to disable recursive cloning? Or do you want a way to configure the scanner to not clone a specific repository recursively? |
@mnonnenmacher there are large repositories included as submodules that should be skipped. Currently there is no way to avoid these to be both downloaded (cloned) and analyzed. |
@dgutson, what @mnonnenmacher was asking is: Do you want this to be a new CLI option to the stand-alone Given that you wrote
I understand that you only want the latter, a way for the scanner (not downloader CLI) to not download Git submodules, and thus omit them from scanning. Maybe we could make path excludes smart to understand that a path refers to a submodule, and then not clone that submodule. |
@arieltorti what do you think? |
I understood the response differently:
As you say "analyzed" my assumption was that you use the downloader to download a repository before running the analyzer. So you would need an option for the download command to not clone recursively, but this would also require changes to the scanner because currently it would still do a recursive clone. However, before we can say if and how this can be implemented we would need to understand the use-case better. |
That will work.
We run |
We would need the ability to exclude the cloning of the (git) submodules of a given repository. I would like to be able to specify that as an exclude in the .ort.yml file. Maybe there could be a section regarding the behavior of the downloader.
The text was updated successfully, but these errors were encountered: