✳flâneur — a map of the web's best reading

Git - git-cherry-pick Documentation

git-scm.com · 1,768 words · saved by 1 readers

Given one or more existing commits, apply the change each one introduces, recording a new commit for each. This requires your working tree to be clean (no modifications from the HEAD commit). When it is not obvious how to apply a change, the following happens: The current branch and HEAD pointer stay at the last commit successfully made. The CHERRY_PICK_HEAD ref is set to point at the commit that introduced the change that is difficult to apply. Paths in which the change applied cleanly are updated both in the index file and in your working tree. For conflicting paths, the index file records up to three versions, as described in the "TRUE MERGE" section of git-merge[1]. The working tree files will include a description of the conflict bracketed by the usual conflict markers >>>>>>. No other modifications are made. See git-merge[1] for some hints on resolving such conflicts. Commits to cherry-pick. For a more complete list of ways to spell commits, see gitrevisions[7]. Sets

Git - git-cherry-pick Documentation English ▾ English Français Português (Brasil) Русский Svenska українська мова 简体中文 Topics ▾ Setup and Config git config help bugreport Credential helpers Getting and Creating Projects init clone Basic Snapshotting add status diff commit notes restore reset rm mv Branching and Merging branch checkout switch merge mergetool log stash tag worktree Sharing and Updating Projects fetch pull push remote submodule Inspection and Comparison show log diff difftool range-diff shortlog describe Patching apply cherry-pick diff rebase revert Debugging bisect blame grep Em

Explore this link on the map →

related reading