Skip to main content
The cherry-pick command allows you to apply the changes from a specific commit into your current workspace without merging the entire branch.
The <ref_id> parameter is the ID of the commit to cherry-pick. The [<paths>...] parameter limits the cherry-pick to the files and folders you name. A folder brings in every change the commit made under it. Leave it out to pick the whole commit. Paths are read relative to the folder you run the command in. Wildcards such as *.png are not supported. [--nowait] returns immediately without waiting for the files to finish syncing to your local workspace. By default, the command waits until the sync is done. This is useful when you want to apply specific changes from another branch without merging everything. An example of cherry-picking a commit:
The changes from commit dv.commit.1042 will be applied to your current workspace. You’ll need to commit these changes to save them to your branch. To pick only part of a commit, name the files and folders you want after the commit ID:
This applies the commit’s changes to src/player.cpp and to everything under Assets/Textures, and leaves the rest of the commit out. If the commit changed nothing under a path you named, the command reports that path and still applies the others. If the commit changed nothing under any of the paths you named, the command fails and your workspace stays as it was. A renamed file belongs to its new path. Picking the new path also clears the old one, and asking for the old path brings in nothing.
If there are conflicts between the cherry-picked commit and your current workspace, you’ll need to resolve them manually. Files that do not conflict are still applied.