Skip to content

Fix analyzing files outside of configured source-paths. #49

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

Conversation

fabiodomingues
Copy link
Owner

Fixes: #48

Checklist

  • I created an issue to discuss the problem I am trying to solve or an open issue already exists.
  • I added a new entry to CHANGELOG.md
  • I updated documentation if applicable (docs folder)

@fabiodomingues fabiodomingues force-pushed the fix-analyzing-files-within-source-paths-not-configured-to-be-analyzed branch 3 times, most recently from 372159d to 966c291 Compare April 2, 2024 11:54
@fabiodomingues fabiodomingues force-pushed the fix-analyzing-files-within-source-paths-not-configured-to-be-analyzed branch from 966c291 to 4d68310 Compare April 2, 2024 14:51
@fabiodomingues fabiodomingues merged commit 5bb3c1d into main Apr 6, 2024
@fabiodomingues fabiodomingues deleted the fix-analyzing-files-within-source-paths-not-configured-to-be-analyzed branch April 6, 2024 13:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Analyzing files within source-paths even when not configured to be analyzed
2 participants