Support Cherrypicking of multiple selected commits at once

Comments: 8

• 29 Aug, '21
  Vladislav Javadov

  There should be an option to select cherrypicking to one squashed commit or keep them one-by-one.

• 08 Feb
  Eli Merged

  It should be possible at GitKraken client to cherry pick multiple commits. For now I need to do it at Git command line and it is annoying.

• 09 Feb
  Jonathan Admin

  "Cherry pick multiple commits" (suggested by Eli on 2022-02-08), including upvotes (1) and comments (0), was merged into this suggestion.

• 10 Feb
  Eli

  ..........

• 16 Feb
  Axel Heider

  Selecting multiple commit should offer to either "do" this or "open selection in interactive rebase view", so the order can be changed there and squashing is possible.

• 18 May
  Francis

  I find it _very_ surprising that selecting multiple commits then rightclicking on one of them only operates on the one you actually right-clicked, instead of the entire set of selected commits!
  
  This really needs better UX. Make sure batch operations are properly supported for the items in the menu, or don't show those items in the right-click menu at all if multiple commits are selected!

• 17 Aug
  Brandon McConnell

  I'm also very surprised this isn't supported. Cherry picking batches of commits should be supported across the board. This would be a huge convenience to the versioning lifecycle process.

• 15 Sep
  Brennan

  I ran into a need for this today, my options were:
  - Manually cherry-pick a long sequence of commits
  - Lookup the relevant git CLI command syntax (`git cherry-pick 7f545188^..a7785c10`), then get the actual commit SHA values for the start and end of the range to use.
  
  The CLI output for me was:
  
  ```
  On branch feat/add-cherry-commit-range-to-this-branch
  Cherry-pick currently in progress.
  (run "git cherry-pick --continue" to continue)
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)
  
  nothing to commit, working tree clean
  The previous cherry-pick is now empty, possibly due to conflict resolution.
  If you wish to commit it anyway, use:
  
  git commit --allow-empty
  
  Otherwise, please use 'git cherry-pick --skip'
  ```
  
  Nothing appeared to happen. But then I tried `git cherry-pick --skip` and got some more output of each commit being applied.
  
  ---
  
  GitKraken could improve that UX? Seems like a feature it could support?