Git Cherry Pick instead of Git Merge

Git Cherry Pick instead of Git Merge

Eddie Jaoude

1 год назад

1,951 Просмотров

Ссылки и html тэги не поддерживаются


Комментарии:

@AllenKenney-gw3fr
@AllenKenney-gw3fr - 08.12.2022 22:06

Thank you! I wanted to know if cherry-picking would preserve the original commit hash from the feature branch or not, and this answered my quesiton. [No, it's a new commit hash]

Ответить
@njong_emy
@njong_emy - 19.10.2022 19:38

I'm hereeeee! Thank you so much for the video Eddie 💜 very informative seconds!

Ответить
@TheHamstertron
@TheHamstertron - 19.10.2022 19:05

I find this useful for when you fix a bug on your branch to facilitate your work but need to release the bugfix before your feature is due for release. You can cherry-pick the fix into the release branch.

To avoid conflicts you can do an interactive rebase to remove the cherry-picked commit from feature, then rebase onto the source branch to pick up the change. Or just solve the conflict if it's not too horrible. The conflicts are the only downside to cherry-pick.

Ответить