I have more Git videos! kzbin.info/aero/PLfU9XN7w4tFwKwh_xPSQ_X1-hROQEpHnM. Additionally, a written reference for this video is available on my blog: www.themoderncoder.com/git/
@subramanyakrishnamurthy83524 ай бұрын
"No nonsense, just get to the point" videos. Very easy to follow and much appreciated!!
@prasanthbupd6 күн бұрын
concise & precise only video worth it you earned a subscriber. thanks BTW I use Arch
@softwaredevx5 ай бұрын
Crystal clear, to the point explanation. Love your teaching style with animations. Please keep on making videos.
@CodeChronicalsАй бұрын
OMG, this is amazing! The way you explain the cherry-pick command with animation made it so easy to understand. It just clicked with me.
@nageshvagicharla3 ай бұрын
Thank you, till now I faced difficulty about cherry picking, but after watching this video it made completely sense. Thanks again.
@mariocalderon21484 ай бұрын
Thank you, amazing! I was always "afraid" of using cherry picking, but with this excellent explanation I will use it often.
@Empea4all7 ай бұрын
Crystal clear, and just what I needed.
@matk22836 ай бұрын
you are the best !! my take way: learned how to check the log of another branch without switching to it. learned the concept of cherry pick love your animation. my great gratitude to you for your time to teach us all this. you must be a very nice person !!. Thanks again ! Mathew. K from Colorado
@smileyboy27008 ай бұрын
Thank you. I was annoying developers with it before but it started to seem too bad so I wanted to take control of it and cherry pick myself so Devs can focus on code. Thank you
@gopikrishna1831 Жыл бұрын
tutorial is clean and crispy
@antonyjere Жыл бұрын
Lovely! Thank you so much for this. You kept it dead simple, which is what we are looking for.
@hacikho8 ай бұрын
Dudede I liked your teaching skills and visualization, and now I understood cherry pick. Awesome. Thanks
@Alex-bc3tt10 ай бұрын
Pure definition of getting straight to the point🙏🙏🙏🙏
@josemartins-jumia Жыл бұрын
You have the best git videos on the all internet. Congrats
@EdchelStephenNini2 ай бұрын
Thank you Jack!!
@brunopagnoАй бұрын
Nice tutorial!
@procrastinator24Ай бұрын
great video! Thanks so much!
@rishu4225Ай бұрын
Good stuff! Many thanks.
@davidmata3104 Жыл бұрын
The best git tutorial Ive ever seen
@ewamewa2436 Жыл бұрын
Well explained, clear and to the point. Thank you 🙂
@__greg__Ай бұрын
awesome and to the point, ty!
@nathanmersha5295 Жыл бұрын
honestly I though I would die before learning cherry pick, thank you for the clear explanation
@vincenguyendev Жыл бұрын
you're amazing , keep it the good work :)
@themoderncoder Жыл бұрын
Thank you!
@SJMilnor Жыл бұрын
Thanks, man. That was an ideal tutorial video. Straight to the point and clear animations to help. You rock!
@yasirirfan526218 күн бұрын
good work.
@TheProtagonist5556 ай бұрын
Wow.. how easily explained!
@SZOKE19940321 Жыл бұрын
the visualization really helps, appreciated!
@gostixxxx Жыл бұрын
Thanks! Very effective explanation. Even my cat now understood 😂
@themoderncoder Жыл бұрын
Lol excellent!
@damaroro Жыл бұрын
straight to the problem, thanks
@sourPollo Жыл бұрын
You made it very easy to understand! Thank you!
@mauro3343 ай бұрын
I've just prepared my first hotfix release using your tips. My tag version is going to be in production next wednesday. 😝
@themoderncoder3 ай бұрын
Nice! Great job 👏
@AVISH7476 ай бұрын
Subscribed...! Thanks a lot.
@nijuyonkadesu Жыл бұрын
Simple and nice explaination !
@megharajdeepak4 ай бұрын
Not sure if I am doing it right. I have 2 branches, dev and main. Let's say dev and main are in sync initially. At at present, my development work in going on and I have added 3 new commits to dev (main now lags by 3 commits). At this point of time there is a production issue and I add a fix on dev and make the 4th commit. After switching to main branch, if I run `git cherry-pick bd46315 `, it's pulling earlier 3 commits along with 4th one. I want to pull only the 4th commit: bd46315 (origin/dev, dev) 4.HOT FIX ADDED ede1f33 3.textarea added 88cdb80 2. select dd added c93667f 1. text input added 62d132f (HEAD -> main, origin/main) Initial commit
@yousufazad69146 ай бұрын
Good video
@moazelsawaf20005 ай бұрын
Thank you so much ❤
@bradburrick8 ай бұрын
Awesome and thank you!
@ronshu123 Жыл бұрын
Very helpful ! Thanks man !
@zakariyaechmaili5647 Жыл бұрын
thanks, clear and straight to the point ♥
@_duongductrong8 ай бұрын
Thank u, so clearly
@marcosradix18 ай бұрын
awesome, thank you!
@khalidsaifullahfuad Жыл бұрын
Short sweet, great tutorial
@themoderncoder Жыл бұрын
Glad it helped
@RahulPalivela-e9l9 ай бұрын
thanks man
@shashankkumar1633 Жыл бұрын
very nice explaination
@pravin1877Ай бұрын
I have question - 3:57 wouldn't it be better, if order of the commit should be old to new commit i.e. bugfix in config followed by added logo to footer. Any thoughts
@emilmathew2257 Жыл бұрын
Awesome video!!
@sim_scape Жыл бұрын
Thank you so much
@p.a87508 ай бұрын
Great video. Quick question - your example shows cherry picking into main. Can we use cherry pick to go from one branch to another (non main) branch?
@themoderncoder8 ай бұрын
Yes, you definitely can.
@imprince95 Жыл бұрын
Very informative, but I have a question, what if we cherry pick a commit that has changes related to a piece of code that was introduced in a commit that we haven't cherry picked, what would happen then? Thanks a lot.
@themoderncoder Жыл бұрын
You’d get a conflict. The cherry pick operation will pause and notify you that it found incompatible changes. You can then choose to fix it or abort the cherry pick. I go over that workflow here if you’ve got time for another video: kzbin.info/www/bejne/l4bIf5WmiNCMbs0si=XY4HdGpHM6_QSU1S
@imprince95 Жыл бұрын
@@themoderncoder Oh I see, will definitely check it out, thanks.
@MalwareAttacker-nc4gx Жыл бұрын
Thank brother
@RecitoGigihPrasidha11 ай бұрын
but in vs code after i do the cherry pick why the changes is not detected? is it only me? or it's supposed to be like that?
@themoderncoder11 ай бұрын
Can you clarify what you mean?
@kanishka_malviya Жыл бұрын
Too simple to not understand :)
@showsshorts46966 ай бұрын
awesome super easy
@RichFinelli5 ай бұрын
At the end when you demo'd multiple commits being cherry picked, the more recent commit was listed first. If the recent commit built on top of the earlier commit, would it make sense to order them by earlier commit first and recent commit second when doing git cherry pick? I.e. git cherry-pick
@themoderncoder5 ай бұрын
Yes! If you're picking multiple I'd keep the same order as they originally were. Sorry - I didn't realize I did them out of order in the video. Good catch.
@KamelJabber16 ай бұрын
Seems too simple when you put it this way
@jeffstone6842 ай бұрын
thanks @themoderncoder! that was very clear and easy to understand. Now I want to know what sorcery you used to copy both of the git hashes onto the clipboard at once 😀
@themoderncoder2 ай бұрын
Lmao, that’s amazing you caught that! I edited that in post because it felt too clunky for the flow of the video to go back and forth copying one then the other. If anybody knows of a tool to do that, I’m all ears too
@rbidАй бұрын
Thanks for the tips. Excellent short video as usual. Greetings from the Galilee.
@bartekz8810 ай бұрын
Will you have a conflict after doing git rebase nav?
@themoderncoder10 ай бұрын
If you rebase nav against main AFTER the cherry pick, you won’t have a conflict because of the cherry picked commit. That said, it depends on what’s in the other commits on the nav branch, but the cherry picked commit won’t cause issues.
@shivamthakur11765 ай бұрын
Straight to the point, easy to understand for the beginners with good animation
@TMDX-j2q6 ай бұрын
Wow, this is a great explanation! Thank you for sharing, helped me a lot to understand how cherry-pick works.
@amoohesam9 ай бұрын
Bro I just subscribed without any hesitation. Thank you for your great work!
@abcdabcd86054 ай бұрын
Amazing explanation. Those animations made it very easy to understand.
@Ahmad_Al-Deeb20 күн бұрын
Thanks a lot! I'm very excited to check your other Git content!
@adipati27maАй бұрын
Best git explanation ever, very clear and just perfect!!
@pabloscloud5 ай бұрын
Thanks, you made it very straight forward!
@AnantaAkash.Podder10 ай бұрын
Well explained man... thanks for making it easy
@sayemalmahdi6691 Жыл бұрын
Thanks man !! Keep up the good works.
@iatheman8 ай бұрын
Top teaching style on these videos!
@irvanhardyanto70383 ай бұрын
Nice explanation, thankyou
@AndresGutierrez-nb6qr7 ай бұрын
Awesome. Gracias 🤝
@joaquimferreira4954 Жыл бұрын
Great tutorial mate, keep it up
@haikalyusuf4058 Жыл бұрын
Hey Jack, thanks for sharing about cherry-pick, I’ve actually been using it at work for the past month I’ve been meaning to ask, in this case, as the commit hashes are different, how would the resulting main branch look after merging the feature branch? I assume there would be 2 duplicate commits of the commits that were cherry-picked?
@themoderncoder Жыл бұрын
That's correct. Cherry pick just applies the changes introduced by the commits - so you're essentially duplicating the commits you've cherry picked. The example I gave in the video about a bug fix commit is deliberate, because that's one common situation where cherry pick is useful; however, most of the time you'll probably find merge or rebase a better tool to apply changes across branches.
@pelvispresley22 Жыл бұрын
wondered how the hell cherry pick worked for years after someone at an internship tried to show me years ago but in the most convoluted way. Now you've made me realize how easy it really is in just 5 mins and actual use cases for it. I was nervous about it for nothing lol thx man!
@themoderncoder Жыл бұрын
Honestly, it’s comments like yours that keep me motivated! Thanks for letting me know
@tzuuyaolee9402 Жыл бұрын
hello Jack, thx for your tutorial.. q: after cherry-pciked, it will be "merged" to the target branch? (or cherry-pick is a temporary solution for me to continue work on a project?)
@themoderncoder Жыл бұрын
You can think of stashes like setting aside your staging area. So unlike branches that can be merged, or commits that can be rebased, stashes aren't anchored to anything so when you say stashes are "merged" they're really just merged into staging area. This means when you pop out stashes there can be conflicts, but that's not quite the same type of conflict as a traditional merge conflict - this video might clear some of that up: kzbin.info/www/bejne/sHSXdZiid9eSfMk
@ehsantavakoli24188 ай бұрын
That was awesome 👍
@kenansenagic3846 ай бұрын
Great tutorial :)
@naktaal Жыл бұрын
Do you think you could make a video where you explain cherry-picking merge commits?
@themoderncoder11 ай бұрын
Should be the same workflow since merge commits are just a bundle of all the changes introduced by that particular branch.