OSAC-4808: Add Ship/Show/Ask risk classification labels - #7
Conversation
Add auto_apply_labels with three mutually exclusive risk labels (risk:ship, risk:show, risk:ask) and a risk classification section in PR summaries. Ported from flightctl with generic criteria that work across all osac-project repos. Labels-only — data-collection phase to validate classifications before enabling merge-path changes. Assisted-by: Claude Code <noreply@anthropic.com> Signed-off-by: Itzik Ezra <iezra@redhat.com>
|
Warning This pull request changes a CodeRabbit configuration file. Because it comes from a fork or its author is not a repository collaborator, reviews use only the configuration from the target branch. The proposed configuration will take effect after it is merged. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review. WalkthroughThe CodeRabbit configuration now requires affected-area and compatibility details in summaries. It also defines mutually exclusive ChangesCodeRabbit policy configuration
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to This PR adds risk-label classification configuration without a demonstrated correctness, security, availability, or deployment issue; no actionable merge-blocking risk remains beyond normal checks and review. Suggested reviewers: 🚥 Pre-merge checks | ✅ 11✅ Passed checks (11 passed)
Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.) Full details: No-Hardcoded-SecretsExplanation PASS: The pull request adds only prose, risk labels, and YAML configuration. The parent-to-HEAD diff contains no API key, token, password, private-key material, credential-bearing URL, encoded blob over 32 characters, or secret-named variable assigned a literal. The words “secrets” and “credentials” occur only in classification instructions. Full details: No-Weak-CryptoExplanation PASS: The pull request changes only Full details: No-Injection-VectorsExplanation PASS: The pull request changes only Full details: Container-PrivilegesExplanation PASS. The pull request changes only Full details: No-Sensitive-Data-In-LogsExplanation PASS: The PR changes only Full details: Ai-AttributionExplanation AI use is present in the PR context and commit. The changed commit includes ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Summary
auto_apply_labelswith three mutually exclusive risk labels (risk:ship,risk:show,risk:ask) ported from flightctlhigh_level_summary_instructionswith risk classification justification (flightctl ref)What changed
Added 115 lines to
.coderabbit.yaml:high_level_summary_instructions— requests a "Risk classification" section in every PR summary with justificationauto_apply_labels: true— enables automatic label applicationlabeling_instructions— detailed criteria for each risk levelmutually_exclusive_groups— ensures only one risk label per PRJira
https://redhat.atlassian.net/browse/OSAC-4808
Test plan
@coderabbitai configurationon this PR to validate schemaSummary by CodeRabbit
Documentation
Workflow