feat(scan): consider .gitignore to automatically exclude paths by default

[rafaela-soares]

Issue #4584 will be closed when the branch release/1.6 is merged into the master.

Proposed Changes

• consider .gitignore to automatically exclude paths by default

I submit this contribution under the Apache-2.0 license.

[roi-orca]

@rafaela-soares I would suggest having the default behavior as of today, meaning .gitignore content will be taken into consideration as part of the scan, and the newly added flag, which can be called "--include-gitignore" will exclude the content from the scan.

If we do that, we do not break the current usage of the CLI, and we are having a "strict by default" approach

[nunoocx]

Please review the suggestions

[rafaela-soares]

@rafaela-soares I would suggest having the default behavior as of today, meaning .gitignore content will be taken into consideration as part of the scan, and the newly added flag, which can be called "--include-gitignore" will exclude the content from the scan.

If we do that, we do not break the current usage of the CLI, and we are having a "strict by default" approach

Hello, @roi-orca!

Thank you so much for being involved in this question and for your suggestion.

It was a product decision to exclude paths specified within .gitignore file by default. A few users suggested that since the .gitignore file presents the files that will be not committed. Since it can be considered a breaking change, this new behavior will be only included from version 1.6. To disable this behavior, you can use flag --add-gitignore.

[nunoocx]

Great work!