Skip to content

Commit

Permalink
fix: cherry-pick order on GitLab by reversing commmit list only once
Browse files Browse the repository at this point in the history
GitLabClient already handle commit order reversing, so re-handle it in
Runner causes cherry-pick order on GitLab to be wrong.

Remove commit order handling from Runner, and instead handle difference
between GitHub and Codeberg inside GitHubClient.

Now, since the default of --bp-branch-name takes the commit list from
{GitHub,GitLab}Client directly, that means backporting branch name
on Codeberg will also be changed to have commits in the correct order
too (old to new, in line with GitHub and GitLab), which is IMO a nice
bonus.
  • Loading branch information
peat-psuwit committed Oct 3, 2024
1 parent fe22142 commit efb9253
Show file tree
Hide file tree
Showing 6 changed files with 2,022 additions and 1,103 deletions.
Loading

0 comments on commit efb9253

Please sign in to comment.