Outcome-based calibration of review prompts #81
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Reference
marvin8/wuming#81
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
There is no feedback loop between what maintainers actually do with findings (fix vs decline) and what the reviewers are prompted to look for. Calibration today is manual and static.
Longer-term, tracking acted-on vs declined findings per project (building on the declined-findings ledger) would allow periodic, data-driven tuning of review prompts per repo. Ambitious and experimental — worth exploring only after the ledger exists.