Skip to content

Commit messages are applied in reverse #32

Description

@akai-hana

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions