Commit messages are applied in reverse
- Dominant language
- TypeScript
- Stars
- 1.4k
- Forks
- 56
- PR merge metrics
- No merged PRs in 30d
Description
Pretty much the title: the commit messages end up applied in the complete reverse order of what they should be.
Grec points to the correct commit hashes during the process, but when I check the new commit history, what should've been the latest commit's message is now the first commit of the repo's message.
I believe this is an issue with how git-filter handles the order of commits, though I may be wrong.
Contributor guide
Research direction
Start by reproducing the issue and trace how git-filter processes commit hashes and assigns messages. Compare the processed order with the resulting commit history; done means each rewritten commit retains the message associated with the corresponding original commit rather than reversing the sequence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100