[GH-ISSUE #97] Rebasing cleans all authorship #42

Closed
opened 2026-03-02 04:11:25 +03:00 by kerem · 4 comments
Owner

Originally created by @AtnesNess on GitHub (Oct 7, 2025).
Original GitHub issue: https://github.com/git-ai-project/git-ai/issues/97

Steps to reproduce

  • Create branch br-1
  • Create branch br-2 and check out to it
echo test > a.txt
git-ai checkpoint mock_ai
git add a.txt && git commit -m 'test'
> git-ai blame a.txt
4138def (some-ai 2025-10-07 13:51:47 -0700    1) test
  • Checkout to br-1
echo test > b.txt
git-ai checkpoint mock_ai
git add b.txt && git commit -m 'test2'
> git-ai blame b.txt
cfc0931 (some-ai 2025-10-07 13:52:49 -0700    1) test
  • Checkout back to br-2
  • Rebase
git rebase br-1

Actual result:

git-ai blame a.txt
d5ef96c (Atnes Ness 2025-10-07 13:51:47 -0700    1) test

As you can see there is no authorship log generated for commit d5ef96c after rebase

However, I still can access old commit sha note with git notes --ref ai show 4138def

Originally created by @AtnesNess on GitHub (Oct 7, 2025). Original GitHub issue: https://github.com/git-ai-project/git-ai/issues/97 ### Steps to reproduce - Create branch `br-1` - Create branch `br-2` and check out to it ``` echo test > a.txt git-ai checkpoint mock_ai git add a.txt && git commit -m 'test' ``` ``` > git-ai blame a.txt 4138def (some-ai 2025-10-07 13:51:47 -0700 1) test ``` - Checkout to `br-1` ``` echo test > b.txt git-ai checkpoint mock_ai git add b.txt && git commit -m 'test2' ``` ``` > git-ai blame b.txt cfc0931 (some-ai 2025-10-07 13:52:49 -0700 1) test ``` - Checkout back to `br-2` - Rebase ``` git rebase br-1 ``` **Actual result**: ``` git-ai blame a.txt d5ef96c (Atnes Ness 2025-10-07 13:51:47 -0700 1) test ``` As you can see there is no authorship log generated for commit `d5ef96c` after rebase However, I still can access old commit sha note with `git notes --ref ai show 4138def`
kerem 2026-03-02 04:11:25 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@svarlamov commented on GitHub (Oct 8, 2025):

I believe rebase isn't supported yet (https://github.com/acunniffe/git-ai/blob/main/docs/limitations.mdx?plain=1#L39) but I'll let @acunniffe chime in

<!-- gh-comment-id:3379322010 --> @svarlamov commented on GitHub (Oct 8, 2025): I believe rebase isn't supported yet (https://github.com/acunniffe/git-ai/blob/main/docs/limitations.mdx?plain=1#L39) but I'll let @acunniffe chime in
Author
Owner

@acunniffe commented on GitHub (Oct 8, 2025):

Yep this is not one of the supported flows but definitely planned and the work on merge --squash verified the core approach

<!-- gh-comment-id:3382607271 --> @acunniffe commented on GitHub (Oct 8, 2025): Yep this is not one of the supported flows but definitely planned and the work on merge --squash verified the core approach
Author
Owner

@acunniffe commented on GitHub (Oct 10, 2025):

See https://github.com/acunniffe/git-ai/pulls

<!-- gh-comment-id:3390165582 --> @acunniffe commented on GitHub (Oct 10, 2025): See https://github.com/acunniffe/git-ai/pulls
Author
Owner

@acunniffe commented on GitHub (Oct 14, 2025):

Fixed in https://github.com/acunniffe/git-ai/pulls?q=is%3Apr+is%3Aclosed

<!-- gh-comment-id:3401435300 --> @acunniffe commented on GitHub (Oct 14, 2025): Fixed in https://github.com/acunniffe/git-ai/pulls?q=is%3Apr+is%3Aclosed
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#42
No description provided.