Skip to content

fix: classify large modifications as feat instead of fix - #1

Merged
zorhehs merged 1 commit into
mainfrom
fix-large-diff-classification
Aug 21, 2026
Merged

fix: classify large modifications as feat instead of fix#1
zorhehs merged 1 commit into
mainfrom
fix-large-diff-classification

Conversation

@zorhehs

@zorhehs zorhehs commented Aug 21, 2026

Copy link
Copy Markdown
Owner

What

Modified files whose total changed lines (additions + deletions) reach
50+ now classify as feat instead of fix.

Why

A 1-line typo fix and a 200+ line rewrite were both landing on fix:
because inferType() only looked at file status (A/M/D), never diff
size.

How I found this

Dogfooded commitcraft on a real project (a 224-line change to
src/app.py) and noticed it labeled a substantial rewrite as fix.

Testing

Added 4 new test cases covering: small diff stays fix, large diff
becomes feat, and the boundary right at/under the threshold.
All 12 tests pass.

A 1-line typo fix and a 200+ line rewrite were both landing on 'fix:'
because inferType() only looked at file status (A/M/D), never diff
size. Modified files whose total changed lines (additions + deletions)
reach largeChangeThreshold (50) now classify as feat.

Found via dogfooding on a real 224-line change (src/app.py in
ai-research-summarizer) that was incorrectly labeled fix.
@zorhehs
zorhehs merged commit 8abe0aa into main Aug 21, 2026
1 check passed
@zorhehs
zorhehs deleted the fix-large-diff-classification branch August 21, 2026 09:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant