fix: add security insights yaml to known maintainers paths#4388
Conversation
Signed-off-by: Mouad BANI <mouad-mb@outlook.com>
PR SummaryLow Risk Overview Repos that publish Security Insights in YAML will get the full-path governance score during candidate ranking, appear in the AI maintainer-file examples, and skip unnecessary section filtering when those paths are selected for extraction. Reviewed by Cursor Bugbot for commit 876ddcf. Bugbot is set up for automated code reviews on this repo. Configure here. |
|
|
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
There was a problem hiding this comment.
Pull request overview
Adds YAML Security Insights filenames to maintainer-file detection.
Changes:
- Recognizes
security-insights.ymlandsecurity-insights.yaml.
Review note: The PR title requires a trailing JIRA key, e.g. (CM-1234).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
This pull request makes a minor update to the
MaintainerServiceclass by expanding the set of recognized security insights files. Now, bothsecurity-insights.ymlandsecurity-insights.yamlare included alongside the previously supportedsecurity-insights.md.security-insights.ymlandsecurity-insights.yamlfiles in the set of recognized security insights files inMaintainerService(maintainer_service.py).