Assessment: Review pipeline stages + config save/tag fixes#217
Merged
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Ayush8923
approved these changes
Jun 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue: #216
Summary
Wizard navigation order
Evaluation step's forward button previously said "Next: Review", but it jumping past to the Post Processing step. Now it says "Next: Post Processing", so the order is Mapper → Eliminatory → Evaluation → Post Processing → Review.
Review Stage previously showed only Dataset, Columns, LLM Input, Configs, and Response Format — the two optional stages were invisible, so a user couldn't confirm what Eliminatory and Post Processing would do (or that they were skipped). Review now also shows:
Eliminatory — Topic Relevance (columns, documents, prompt preview) and Duplicate Detection (columns). Shows "Skipped" when nothing is enabled.
Post Processing — computed columns, filters, and sort rules. Shows "Skipped" when nothing is configured.
Saving an Evaluation config
When saving a new config, the old code looked for an existing config with the same name and, if found, created a new version under it instead — wrong behavior, since this is the "New" flow. Now it always creates a new config, so a duplicate name correctly raises a name-conflict error.