Note that cherry-pick will copy the commits so that the original commit will still be present in the source branch. Most devs will consider cherry-picking is a bad practice that can cause problems like having duplicate commits in multiple branches, messing up with the git history, and others.

Is git cherry-pick safe?

2 Answers. It is safe, as the cherry-pick only takes the changes of the commit identified as c2 . However, as stated in the comments, this might cause problems if the c2 change depends on previous changes between c2 and c1 .

Does git cherry-pick Create a new commit?

Using git cherry-pick The command git cherry-pick commit applies the changes introduced by the named commit on the current branch. It will introduce a new, distinct commit. Strictly speaking, using git cherry-pick doesn’t alter the existing history within a repository; instead, it adds to the history.