Відео

thanks for the video!

Thanks bro you just saved me

At 5:06, I didn't get the idea why we checked out to feature branch for rebase to work. Aren't we actually doing it as following: "Change the base of your feature branch to the latest commit (head) of the master branch"..? I'm a bit confused here, pls help.

Your videos are an absolute gem. Thank you

Linus Torvalds and Ada Lovelace. You have friends in high places 🙂

3:09 You lost the instagram_username line from the bugfix commit LOL.

Beast video! Thanks.. I just got my new mac today and this video helped alot!

dude! so envy about the city, nice content tanks a lot for sharing

Great class! Thank you!🙏🏼

this is so helpful, thanks man

gooog

6 years later and this is still an amazing video! Super clear and intuitive, thank you!

Nice format. Thanks

git config --global rerere.enabled true git config --global pull.rebase true That’s the way

Nice explanation, thankyou

Crystal clear ! I'm glad I've found your channel and eager to discover more

Excellent explanation and a nice, clean video. Well done. Subbed

Excellent videos, have been using git but I had lot of confusion about many basic concepts, luck i came across your videos with very crisp explanation with awesome graphical representation which makes it very easy to understand. Keep up the good work, looking forward for more informative videos..

SUPERB... Video. Crisp and upto the point. Nugget sized videos - addressing specific topics THANK YOU SO MUCH This video saved me a lot of reading and researching time

I came to Git from SVN -- and the ability to modify history was probably the hardest thing to wrap my head around. Not only that it was possible, but that there were situations where it is actually desirable! Now ... well, I could not go back to SVN! 🙂

Thank you, till now I faced difficulty about cherry picking, but after watching this video it made completely sense. Thanks again.

How do you make such beautiful animated presentations?

Hoping I see you point out rebase leaves a clean tree, merge creates new commits.

I always merge latest from main/dev branch into my feature branches, so my feature branches always up to date. Then PR into main/dev branch when I’m done with a feature

Nice edit and animation

To clarify a common misconception: A "tree" in the context of Git does not refer to a commit history (because that is not in fact a tree in the mathematical sense due to merges, actually it's a DAG) but it refers to a snapshot of the repo, i.e. the content of a commit and therefore a filesystem tree. That might be important to know so not to get confused when reading the Git docs and learning about the Git working tree.

It's simple, never fucking rebase. The very concept of rebasing is fundamentally flawed and only used by damaged OCD people.

شكرا جزيلا .. thanks' a lot man

I think you may have an incorrect mental model of vim. The escape is not part of the quit command. The default mode in vim is the command mode. i puts you into insert mode and escape leaves insert mode and returns you to command mode. Colon moves you to another mode: ex mode where you can type ex commands. The ex command you're using in this situation is wq. If you're using escape before quitting even when in command mode, then it suggests you're not thinking of insert mode as something you dip in and out of before returning to the steady state of command mode and possibly missing out on the incredible power of command mode.

9:15

This is a clear explanation. Very good.

if we are using vi config.yml for vim ide , what command we will use for vs code ide?

Production quality is remarkable.

Fantastic explanation, resolved all my confusion about merging. Thanks

This isn't even close to being definitive... It skips over so many features that git provides for managing conflicts.

Great content! What are you using to make slides?

This is honestly the best git course in all UA-cam. Thank you so much!

So we merge after rebase? just rebase and push is bad practise? Please clarify. Thanks!

in my almost 15 year of using Git, this is by far the best video on how to use merge and rebase. thank you!

very cool , thank you !!!

As a single dev , I only ever use rebase amd NEVER merge just to keep the history strictly linear , however this is a luxury that larger teams might not have . The tip about only using rebase for your own local work is 100% the right way to use it , imo .

My guy at the very beginning when you described git pull as being a combination of fetch and merge...it already instantly clicked for me xD thank you!

Nicely done, thanks my dude.

new subscriber. best explain very very very nice

Thank you a lot for this brother!

I always squash and never allow teammates to work on my branch. This way you maintain main branch clean with only feature commits and avoid conflicts with teammate locally. The only use case I had was when I was introducing a big feature >100 files and split my PR into 6, then I was rebasing branches in order of building block of the feature, where last branch was rebased into main feature branch after reviews of my peers.

Git mergetool is also useful

Best explanation

Please can u provide commads also

perfect