highlight 'per-class' in confidence mode descriptions - #2998
leeclemnet wants to merge 1 commit into
Conversation
|
👋 Thanks for the pull request! Here is how automated Claude review works here, so you spend credits (and reviewer time) wisely. 🚦 This PR is marked Ready for review, so automated Claude review will run — and every pass spends real credits. Warning 💸 The Claude reviewer bills in credits, not vibesAutomated review spins up a real agent that reads real code and spends real credits on every pass. It is glad to help — but it is not a rubber duck, a linter you poke in a loop, or a substitute for reading the contributing guide. Treat it like an expensive senior reviewer whose time you booked, and show up prepared. Draft when unsure, Ready when you mean it:
However you get there, arrive prepared:
Reviews are not free. A draft costs nothing to review; a Ready PR is a promise that it is worth reviewing.
|
|
🤖 Claude review started at commit New commits are not auto-reviewed. Add the |
|
Skills: review-workflows-blocks, review-topic-prediction-integrity Reviewed the change: all 10 hunks are the identical description edit for the "Best" confidence mode ( The new "per-class" wording is accurate: Reviewed at HEAD: b3b53fb |
|
😎 PR passes the vibe-check and trust-me-bro verification. |
What does this PR do?
For model blocks supporting "Best" confidence mode, explicitly mention per-class confidence in the description. This is to address field eng feedback that the per-class nature of this mode was not obvious.
I did not add "Per Class" to the parameter name in the dropdown because it was too wide for the available space and was cut off.
Type of Change
Testing
I have added/updated tests for this changeno test update neededTest details:
Checklist
Additional Context