fix(post): default AR_SEVERITY_FLOOR to warning (#6) #17
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/severity-floor-default-warning"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
AR_SEVERITY_FLOORflips fromnotetowarning. Notes are LLM scratchpad — useful inside the pipeline (the schema keeps them and the LLM can still emit them) but pure noise on the PR page once the verifier has run. PR #4 surfaced 16 LGTM-style notes across 3 review cycles.parse_severity_floorextracted fromseverity_floor_from_envso the value matrix unit-tests without touchingstd::env.warninginstead ofnote, with a warn log; a typo no longer silently inverts the operator's signal-to-noise expectation.docs/OPERATIONS.md§7.2.5,QUICKSTART.mdenv table,deploy/systemd/auto_review.env.example,deploy/helm/values.yaml. CHANGELOG### Changedentry added.Closes #6.
Test plan
cargo test -p ar-orchestrator— 38 passed (5 new severity-floor cases)cargo clippy --workspace --all-targets -- -D warningscleancargo fmt --all -- --checkcleannotedefault: setAR_SEVERITY_FLOOR=notein env to restore previous posting behaviourThis PR changes the default
AR_SEVERITY_FLOORfromnotetowarning, reducing noise on PR pages by default. The change is well-documented across the codebase, and tests have been added to ensure the new behavior is correctly implemented. The PR appears safe to merge, but users relying on the previous default should be informed.Walkthrough
AR_SEVERITY_FLOOR.AR_SEVERITY_FLOORtowarning.parse_severity_floorfunction to handle parsing and defaulting logic. Added tests to verify the new default behavior.AR_SEVERITY_FLOOR.Pre-merge checks
💡 Note: The default value for
AR_SEVERITY_FLOORhas been updated towarning. Ensure that this change is communicated to users who might rely on the previous default ofnote.💡 Note: The function
parse_severity_floornow defaults toWarningfor unrecognized values, which is a change from the previous behavior. This is a safer default but ensure that this change is well-documented to avoid confusion.💡 Note: The test
severity_floor_defaults_to_warning_when_unsetensures that the default behavior is correctly set toWarning. This is a good addition to verify the new default behavior.💡 Note: The Helm chart documentation now reflects the new default for
severityFloor. Ensure that users are aware of this change, especially if they have customized this setting in their deployments.💡 Note: The systemd environment example now reflects the new default for
AR_SEVERITY_FLOOR. Ensure that users are aware of this change, especially if they have customized this setting in their deployments.💡 Note: The operations documentation now reflects the new default for
AR_SEVERITY_FLOOR. Ensure that users are aware of this change, especially if they have customized this setting in their deployments.