Partly cherry-picking a commit with Git

Question

I'm working on 2 different branches: release and development.

I noticed I still need to integrate some changes that were committed to the release branch back into the development branch.

The problem is I don't need all of the commit, only some hunks in certain files, so a simple

git cherry-pick bc66559

does not do the trick.

When I do a

git show bc66559

I can see the diff but don't really know a good way of applying that partially to my current working tree.

score 953 · Accepted Answer · edited Dec 09 '21 at 05:35

953

The core thing you're going to want here is git add -p (-p is a synonym for --patch). This provides an interactive way to add in content, letting you decide whether each hunk should go in or not, and even letting you manually edit the patch if necessary.

To use it in combination with cherry-pick:

git cherry-pick -n <commit> # get your patch, but don't commit (-n = --no-commit)
git reset                   # unstage the changes from the cherry-picked commit
git add -p                  # make all your choices (add the changes you do want)
git commit                  # make the commit!

(Thanks to Tim Henigan for reminding me that git-cherry-pick has a --no-commit option, and thanks to Felix Rabe for pointing out that you need to git reset. If you only want to leave a few things out of the commit, you could use git reset <path>... to unstage just those files.)

You can provide specific paths to add -p if necessary. If you're starting with a patch you could replace the cherry-pick with apply.

If you really want to git cherry-pick -p <commit> (that option does not exist), you can use

git checkout -p <commit>

That will diff the current commit against the commit you specify, and allow you to apply hunks from that diff individually. This option may be more useful if the commit you're pulling in has merge conflicts in part of the commit you're not interested in. (Note, however, that checkout differs from cherry-pick: checkout tries to apply <commit>'s contents entirely, while cherry-pick applies the diff of the specified commit from it's parent. This means that checkout can apply more than just that commit, which might be more than you want.)

edited Dec 09 '21 at 05:35

user664833

18,397
19
91
140

answered Oct 06 '09 at 14:51

Cascabel

479,068
72
370
318

1

Actually, if I follow the advice with git 1.7.5.4, 'git add -p' says 'No changes' because it's all already in the index. I need to do a 'git reset HEAD' before 'git add' - any way to avoid that reset with some option? – Felix Rabe Jan 02 '12 at 09:55
@FelixRabe: I'm actually surprised that at some point `cherry-pick -n` apparently *didn't* leave the changes staged - the convention is definitely that `--no-commit` options stop *right* before the commit, i.e. with all the changes staged. I'll add the reset into the answer. – Cascabel Jan 02 '12 at 15:14
2

@Blixt That is, if the commits that are on the other branch but not your current branch are A-B-C-D-E-F, `git checkout -p ` does *not* just get you the changes from F, it gets you ABCDEF all mashed together and lets you sort out what part of that you want. Paring that down to just some of the changes from F is a pain. On the other hand, `git cherry-pick -n ` gets you only the changes from F - and if some of those changes conflict, it helpfully tells you so that you can figure out how to merge properly. – Cascabel Oct 02 '14 at 19:18
I had problems with this when the change was a file addition. The `git reset` would remove the staged files and the `add -p` would just say 'nothing to add'. – Ian Grainger Sep 06 '16 at 11:45
Note that this method doesn't retain the original commit author and commit date. You can set these with `git commit --author="USER " --date="DATE"`, use the author and date details shown on top of `git show CHERRY_PICK_SHA`. – Tim Visée Oct 16 '20 at 09:55

score 87 · Answer 2 · edited May 23 '17 at 12:03

87

I know I'm answering an old question, but it looks like there's a new way to do this with interactively checking out:

git checkout -p bc66559

Credit to Can I interactively pick hunks from another git commit?

edited May 23 '17 at 12:03

Community

1
1

answered Jun 29 '13 at 04:46

Mike Monkiewicz

4,481
1
22
19

1

Yeah, I've used/discovered this method already. Note that it doesn't create a commit, you have to do that yourself, and there's no quick way to make it auto-record in the commit msg what stuff was cherry picked (this way). Kludgy, kludgy git. – Fizz Jan 22 '22 at 11:27
2

Note that this doesn't just apply (or offer to apply) changes from that commit, but all changes since the branches diverged (at least in Git 2.25.1). – Paŭlo Ebermann Aug 01 '22 at 08:25
Yes, this is not a cherry-pick at all. – haridsv Jul 18 '23 at 06:10

score 36 · Answer 3 · answered Feb 01 '10 at 06:06

36

Assuming the changes you want are at the head of the branch you want the changes from, use git checkout

for a single file :

git checkout branch_that_has_the_changes_you_want path/to/file.rb

for multiple files just daisy chain :

git checkout branch_that_has_the_changes_you_want path/to/file.rb path/to/other_file.rb

answered Feb 01 '10 at 06:06

Jay Swain

738
6
6

5

That copies the whole file: not only the changes. – Jeremy List Mar 26 '14 at 03:02
1

This answer, just as any other answer here so far, has a big drawback: it doesn't preserve the original author of the change, instead committing under your name. If a change is good, you're stealing somebody's credit, if a change is bad, you're putting yourself on the fire. It seems there's no way around having git cherry-pick -p, and shame it's still not there. – pfalcon Oct 29 '15 at 08:28

score 15 · Answer 4 · edited May 23 '17 at 12:18

15

Building on Mike Monkiewicz answer you can also specify a single or more files to checkout from the supplied sha1/branch.

git checkout -p bc66559 -- path/to/file.java

This will allow you to interactively pick the changes you want to have applied to your current version of the file.

edited May 23 '17 at 12:18

Community

1
1

answered Oct 24 '14 at 12:48

Christian.D

879
1
9
21

6

This is problematic if the current version of the file is significantly different from that version. You will be prompted with numerous irrelevant changes (which do not appear in the commit). Also, the changes you really want may appear in a "disguised form" as a difference to the current, not the original difference. It's possible that the original difference you want conflicts, and has to be properly merged; you won't have that opportunity here. – Kaz May 11 '15 at 14:32

nyanpasu64 · Answer 5 · 2019-08-18T04:41:12.890

2

If you want to specify a list of files on the command line, and get the whole thing done in a single atomic command, try:

git apply --3way <(git show -- list-of-files)

--3way: If a patch does not apply cleanly, Git will create a merge conflict so you can run git mergetool. Omitting --3way will make Git give up on patches which don't apply cleanly.

edited Aug 18 '19 at 04:41

answered Aug 18 '19 at 04:00

nyanpasu64

2,805
2
23
31

1

Use the equivalent `git show -- list-of-files | git apply --3way -` if your shell chokes on `<(...)` – raphinesse Feb 16 '22 at 14:07

score 1 · Answer 6 · answered Mar 16 '20 at 22:24

1

Use git format-patch to slice out the part of the commit you care about and git am to apply it to another branch

git format-patch <sha> -- path/to/file
git checkout other-branch
git am *.patch

answered Mar 16 '20 at 22:24

adrock20

175
1
7

score 0 · Answer 7 · edited Dec 16 '18 at 00:51

0

If "partly cherry picking" means "within files, choosing some changes but discarding others", it can be done by bringing in git stash:

Do the full cherry pick.
git reset HEAD^ to convert the entire cherry-picked commit into unstaged working changes.
Now git stash save --patch: interactively select unwanted material to stash.
Git rolls back the stashed changes from your working copy.
git commit
Throw away the stash of unwanted changes: git stash drop.

Tip: if you give the stash of unwanted changes a name: git stash save --patch junk then if you forget to do (6) now, later you will recognize the stash for what it is.

edited Dec 16 '18 at 00:51

Mihai Chelaru

7,614
14
45
51

answered May 14 '14 at 05:25

Kaz

55,781
9
100
149

If you just cherry-pick, then reset... you won't anything to stash. As said above, you have either to do a cherry-pick with --no-commit, or a reset --hard HEAD~. Note that you are proceding negatively (selecting what you don't want). The above accepted solution allow either a positive or a negative approach. – Pierre-Olivier Vares Oct 02 '14 at 07:47

score 0 · Answer 8 · answered Jan 27 '21 at 15:47

Actually, the best solution for this question is to use checkout commend

git checkout <branch> <path1>,<path2> ..

For example, assume you are in master, you want to the changes from dev1 on project1/Controller/WebController1.java and project1/Service/WebService1.java, you can use this:

git checkout dev1 project1/Controller/WebController1.java project1/Service/WebService1.java

That means the master branch only updates from dev1 on those two paths.

Partly cherry-picking a commit with Git

8 Answers8

Linked

Related