feat(scan):SP-4027 add support for scan tuning parameters#54
feat(scan):SP-4027 add support for scan tuning parameters#54agustingroh merged 1 commit intomainfrom
Conversation
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📝 WalkthroughWalkthroughVersion and container image updates across task configuration files and source code. CHANGELOG.md and documentation updated for v1.6.0 release. Runtime container image bumped from v1.40.1 to v1.45.0. Documentation added for scan tuning parameters and Dependency Track integration with SBOM upload status checks. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Suggested labels
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
ed2624c to
9ac1da3
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@OVERVIEW.md`:
- Line 221: Update the wording in the sentence that currently reads "GitHub
Action" to use the correct ADO terminology (e.g., "Azure DevOps task" or "ADO
extension") so it reflects this repository's integration; locate the sentence in
OVERVIEW.md where it says "Scan tuning parameters must be configured through the
`scanoss.json`. They are **not** configured as GitHub Action input parameters."
and replace "GitHub Action" with "Azure DevOps task" (or "ADO extension") to
correct the copy-paste error.
🧹 Nitpick comments (1)
CHANGELOG.md (1)
10-15: Consider adding more detail to the "Added" entry to clarify which tuning parameters were added.The changelog entry is correctly formatted and scanoss-py v1.45.0 was confirmed to exist (released February 2, 2026). However, the "Added" description is generic. Based on the scanoss-py v1.45.0 release notes, specific parameters were added including
--min-snippet-hits,--min-snippet-lines,--ranking,--ranking-threshold, and--honour-file-exts. Consider updating the entry to be more descriptive:
- "Added support for scan tuning parameters (min-snippet-hits, min-snippet-lines, ranking, honour-file-exts) and ScanSettingsBuilder for configuration management"
This helps users understand the feature scope without consulting external documentation.
9ac1da3 to
0d74408
Compare
Summary by CodeRabbit
New Features
Documentation
Chores