GitKraken Tutorial: Crash Course on How to Use Git and GitKraken for Beginners

[@Henrikh2011]

This is definitely one of the best Git - Gitkraken videos I've seen. Although you have kept it at a natural speaking pace - without cutting out speech breaks. Thus, the learning brain can follow along without stressing out. Really enjoyable and educational - BIG thanks for that 🙂

[@cameronmcnz]

OMG. That's so funny you should say that because the obsessive need for people to cut out every speech break and do 20 jump cuts per minute annoys the life out of me. Given, I could probably remove an 'um' or a 'so' every once and a while, but I kinda wish people felt comfortable enough just to talk normally in their videos. Regardless, thanks a lot for the kind comments. I really enjoyed putting this tutorial together. GitKraken is an awesome tool!

[@Sage.highstrike]

Love these tutorials and we GREATLY appreciate you!

[@cameronmcnz]

Thanks for the kind words! I had a lot of fun learning GitKraken and then putting this tutorial together. It's a great tool and more people need to learn it!

[@SauravR402]

Your passion to explain the concepts beautifully in detail is quite astounding. Thanks 😍

[@cameronmcnz]

Thanks for your kind words! Comments like that motivate me to keep going and doing more!

[@teetanrobotics5363]

Awesome tutorial. Thank you so much !! Also request you to make courses on other software engineerining topics like Nginx, redis and kafka

[@cameronmcnz]

Thanks! I loved making it. I wish more people would use GitKraken. (And I wish more people would watch this video too!)

[@unhandledexception1948]

fantastic content, a engaging teaching style.... love this video

[@cameronmcnz]

As always, there's a corresponding GitKraken tutorial over on TheServerSide: www.theserverside.com/blog/Coffee-Talk-Java-News-Stories-and-Opinions/GitKraken-tutorial-for-beginners

[@cameronmcnz]

If you do git reflog you will still see them and can reset back to them. Rarely does anything disappear locally in git. But, if you pushed to GitHub, those commits world not be pushed. Nobody else will see them. I offer call them orphaned commits. They are there but not part of an actual branch history.

[@ivanphone4917]

Nice GitKraken tutorial. The gitkraken GitHub integration was super interesting.

[@cameronmcnz]

It's my favorite part of the whole GitKraken tutorial!

[@eugenetapang]

Cameron, absolutely brilliant, sold on gitKraken, next time add the Philippines branch, woot. :>

[@cameronmcnz]

Forget about a measly branch, the Philippines deserves their own repository! Glad you enjoyed it, and thanks for watching!

[@dougamolina]

Amazing video, thanks a lot!

[@cameronmcnz]

Meh. Git Kraken is an amazing tool. All I did was record myself clicking some buttons. Thanks for watching and thanks for the kind words. And enjoy your journey into DevOps and the Git space!

[@DrCharmsTV]

I love your style of teaching, great tutorial! great teaching! It was a pleasure listening to you. Thank you very much, that's a sub! +1

[@cameronmcnz]

Thanks so much! I honestly love Git and I think GitKraken is awesome. Kinda disappointed that this video has so few views. I worked so hard on it!!!

[@premium-kosher-mobile]

Great guide, thank you!

[@laurentdavenne4864]

Thank you!

[@cameronmcnz]

All the thanks go to the people at GitKraken for the awesome tool. All I did was click come buttons while I recorded the screen.

[@laurentdavenne4864]

@@cameronmcnz However they don't explain it as well as you, so Thank you too. I did 51% of the Foundations of Git - Certification Course... Then I watched your video, thank god I did...

[@cameronmcnz]

@@laurentdavenne4864 Well I am sincerely humbled by your comment. Thanks!

[@xaiga29]

"Also, if you break the build they'll know who to shout at" 😂🤣

[@cameronmcnz]

I've been shout at a lot!

[@ismailriyaz9855]

I learned a lot from your videos. Thank you 😊

[@cameronmcnz]

Thanks for your kind words! Hopefully this GitKraken tutorial will get a lot of people on board with this awesome Git GUI tool!

[@samholmes1684]

This is such a good tutorial. Thanks cameron!

[@cameronmcnz]

Thanks! I really tried to cover as much as I could without overwhelming you. Think I need to do something similar for GitHub or GitLab to rake in more views.

[@user-fh9ot3vk2z]

the video is soooooooo amazing!!!!

[@cameronmcnz]

Thanks! I took a lot of pride in putting this Git and GitKraken tutorial together. A bit disappointed that it's got so few hits. Gonna try sharing on social media more to boost the algo. Thanks for watching!

[@DevendraGuptaProfile]

Cameron, very clear explanation, I would be grateful if you could please answer a short question when you merged africa into main, main already had egypt.txt from middle east, then how it merged, shouldn't it show conflict?

[@cameronmcnz]

A conflict will only occur if the same file has been edited by two different people at the same time, since the last commit. So if a file is in one branch, and someone merges a bunch of files from another branch, Git leaves the existing files alone, and adds in any new files. If two people haven't been editing the same file between merges, there's not to conflict on. Does that make sense?

[@DevendraGuptaProfile]

@@cameronmcnz Thankyou for your prompt reply, i understood what you say, the conflict would have only been occured if egypt.txt has been modified in either or both branches. I hope i uderstood it right.

[@cameronmcnz]

@@DevendraGuptaProfile Yup, by at least two. If just one branch updates it, then it's fine. If only one person is editing it and doing a commit, we know the latest commit is good. If someone merges, we take the updates in the merge, and keep the latest changes the other person has been doing on the file. One person editing a file is fine. No conflict. Only if two people are editing the same file since the last commit is there an issue.

[@DevendraGuptaProfile]

@@cameronmcnz Many Thanks Cameron 😊

[@odin-project]

very concise and informative video tutorial. Hope you can make a video using gitkarken in linux. Thank you.

[@jamescrane9333]

Excellent - thanks

[@cameronmcnz]

Thanks for the kind words! I worked hard on this one!

[@Mohamed-Ramadan-elmazien]

thanks :)

[@cameronmcnz]

Thank the people at GitKraken, they're the ones that put together this awesome Git GUI tool. All I did was click a few buttons.

[@unhandledexception1948]

@13:40 Git Reset example (before you made use of tags to mark a commit), did you effectively after the hard reset totally lose those few commits that had happened after ? or are they still recoverable even without the tag?

[@cameronmcnz]

Just saw this comment! The commit is still there. If you do a git reflog you will see the commit you reset and can reset back to it if u like. Hit keeps everything!

[@abc00607]

Nice!

[@cameronmcnz]

Thanks! Did you notice the Kraken monster in the background?