[PR #71] Handle unstaged / staged changes #238

Closed
opened 2026-03-02 04:13:03 +03:00 by kerem · 0 comments
Owner

Original Pull Request: https://github.com/git-ai-project/git-ai/pull/71

State: closed
Merged: Yes


A user reported that unstaged changes were being considered staged when generating authorship logs.

  • This caused misattribution by shifting many of the line #s
  • No attribution unstaged AI changes in the next commit (once staged)

This PR solves this by

  • Filtering authorship log to only include authored hunks
  • Seeding new commit with a first entry in the working log that attributed unstaged code to AI/human.
**Original Pull Request:** https://github.com/git-ai-project/git-ai/pull/71 **State:** closed **Merged:** Yes --- A user reported that unstaged changes were being considered staged when generating authorship logs. - This caused misattribution by shifting many of the line #s - No attribution unstaged AI changes in the next commit (once staged) This PR solves this by - [x] Filtering authorship log to only include authored hunks - [x] Seeding new commit with a first entry in the working log that attributed unstaged code to AI/human.
kerem 2026-03-02 04:13:03 +03:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/git-ai#238
No description provided.