Support Cherrypicking of multiple selected commits at once
Select a commit range using Shift-Click or Select multiple commits using Ctrl-Click
Select Cherrypick from the context menu
Comments: 26
Oldest
•
Newest
•
Most likes
•
Fewest likes
-
15 Sep, '22
BrennanHighlighted comment
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? -
29 Aug, '21
Vladislav JavadovThere should be an option to select cherrypicking to one squashed commit or keep them one-by-one.
-
08 Feb, '22
Eli MergedIt 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, '22
Jonathan System"Cherry pick multiple commits" (suggested by Eli on 2022-02-08), including upvotes (1) and comments (0), was merged into this suggestion.
-
16 Feb, '22
Axel HeiderSelecting 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, '22
FrancisI 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, '22
Brandon McConnellI'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.
-
07 Mar, '23
YvesNot sure it's a good idea to squash cherry-picked commits. Git will not recognize the squashed commit to be equivalent to the original cherry-picked commits and will cause conflicts headaches.
-
11 Mar, '23
AbdullahSupport cherrypicking of multiple selected commits at once now and I'll pay to upgrade now
-
19 Jun, '23
JeremyYou guys have the time to create Boards and Timelines but can't implement this simple QOL suggestion in 2 years? C'mon now.
-
30 Aug, '23
bcardiffAt least stop moving the focus to the new commit would help. Currently cherrypicking multiple commits involves scrolling down again to the original commits since after each cherrypick the focus is moved to the new commit
-
14 Sep, '23
BramWhat I personally do sometimes as a workaround is,
git cherry-pick <from-hash>^..<to-hash>
this will cherry-pick all commits from the first to the last commit hash, including the from-hash and to-hash. -
26 Sep, '23
JackyPlease vote this issue for yourself and ourselves.
This would be a huge convenience to the versioning lifecycle process.
Many free GitTools had this function already, it really makes our daily work more efficiently absolutely. -
05 Mar, '24
ArianeReally hope they add this soon. It would be a huge time saver when you need to recreate a whole branch because you made a messed-up merge a zillion commits ago. Right now the only two solutions I know of are:
- Take an eternity to right click & cherry pick every commit, making sure they're in the right order and you're not forgetting any
- Copy-paste the whole content of modified files in your new branch. -
22 Mar, '24
ChrisOur team frequently has to cherry pick from dev to release branches, which is pretty standard for many teams. How is this feature not implemented yet despite your own blog saying git does it as far back as 1.7.2?
https://www.gitkraken.com/learn/git/problems/cherry-pick-multiple-commits -
12 Feb, '25
RamsayThe article you linked says that it's possible to cherry-pick multiple commits using the terminal and I can confirm that this works. It's the lack of functionality within the graph that's missing. I personally wish that I could select multiple commits in the commit graph and "Cherry-pick 6 commits" or however many I need.
-
11 Mar, '25
Trevor AdminI’m happy to share that you can now cherry pick multiple commits in GitKraken Desktop 10.8.0! When selecting multiple commits in the Commit Graph, right click on any selected commit to find an option to cherry pick all selected commits. Cherry picking multiple commits will open an interactive cherry-pick tool where you can reorder, squash, and more before applying. You can read our release notes for more details:
https://help.gitkraken.com/gitkraken-desktop/current/#version-10-8-0
Thank you for providing feedback to help improve GitKraken Desktop! -
12 Mar, '25
12SidedPolyhedronYou guys totally made my day with this one.
It's been a paper cut issue for me forever.
But now y'all have enabled my scatterbrained (branch, rebranch, stash, rebranch, redo half the work by hand, reset, try something else, stash, rebranch, do more redundant work, apply stash with conflicts that are not really conflicts because they're identical after I re-did the work, rebase, rebranch, rebranch, cherrypick 30 random commits from across all of it a week later) habits, and I thank you for it! 😅