Following are some cases in which git cherry-picking is useful:
- When you accidentally commit something to the wrong branch;
- When developing features in parallel, where you may need to include a feature from another branch that another person might be developing;
- When you may need to patch a critical bug on production environment, while the feature development might still be ongoing;
- When you may need a specific commit from a stale pull request (that was closed without being merged).
In most other cases, using traditional merges is usually the preferred way. This is because cherry-picking can result in duplicate commits, and may not always be the best practice.
Hope you found this post useful. It was published . Please show your love and support by sharing this post.