fix: v3.0.1 — Gemma summary fallback#120
Merged
Merged
Conversation
Stop caching generic summaries from weaker models like Gemma, fall back to diff-based summaries when summarization fails, and use repo-relative paths for staged diffs. Bump version to 3.0.1. Co-authored-by: Cursor <cursoragent@cursor.com>
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
1 participant
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.
Summary
diffIndexWithHEADWhy
Gemma (and similar models) often return generic summaries like "no changes". Those were cached before filtering, so every retry reused the same useless summary and commit generation failed even with valid staged diffs.
Test plan
pnpm run buildpnpm test(43 passing)Made with Cursor