I am afraid to do git cherry-pick without the -n parameter because cherry-picking automatically commits after picking the changes. Most of the time I want to review the changes and commit them manually. So I do:
git cherry-pick -n HASH
ooh, i wasn't aware of the dry run. I tend to not care because I can always do an interactive rebase and delete those commits.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.