Git for Professionals Tutorial - Tools & Concepts for Mastering Version Control with Git

thanks :")

I closed my eyes for a moment there and I believe it was truly Christoph Waltz teaching me about Git.

learned a lot

the perfect "commit" - topic is more a philosophy. Invented by somebody who mainly focused on software development. - God luck you will need it!

In the real world, git repositories are nearly everywhere. In every CI/CD Pipeline, in Cloud environments and settings for server system configurationfiles, just to mention some.

Nobody gonna start to write a commit message like a book only for the sake of understanding.

mainly you will see a ticket number and your ticket system will tell you what's the story. And you aren't a real professional IT if you don't understand whats goning on if you look a the code...

Isn't rebase cause conflict issue ?

Merge vs rebase explanation was good. No new info for me in previous parts.

git add -u; git commit -m "save"

:P

As a MERN stack developer, should i have to master git version control? I mean most of the things alike pull security and merge, managing branches etc. Please help me!

I write code in work but also at home, everyday. Are there any other solution apart from commit?

La forma en que narraste todo el concepto es tan increíble que todo se quedó perfectamente en la mente.

I’m imagining Christoph Waltz narrating this, they have the same voice😂

Hi Sir How can we know the parent branches
which is tracking to origin of origin

That was such a great video!. I definitely have more confidence now dealing with Merge Conflicts! Thanks Tobias!

Fuc*** amazing....

why the arrow in the visualization is reversed? What I got from the video is that C1 is starting commit, C2 is the next but why the arrow has the direction from C2 to C1?

What a useful guideline. Highly recommend to anyone who's learning git, as it provides so many insights

you sound like Christoph Waltz

Best merge tool: kdiff3!
Saved me for a huge merge involving thousands of conflicts over ~100 files, most of which were just different tab/space conventions, but many conflicts were actual conflicts where I had to combine the two versions.
It shows the last common ancestor, the two versions in the branches to be merged, and the version that will be the output; the output version can also be a mix of all the versions, and can include also new modifications.
It has shortcuts to solve the conflicts fast. It allows to realign the code history with anchors in the two branches manually in case the tool didn't do it properly (even though it is not perfect).

The tutorial is bit confusing.... please include more practical and real life examples. Thank you

This guy needs his own ASMR channel.

Thanks a lot! Smooth voice.

Excellent presentation, excellent explanation. More content from Tobias please 👍

'tobidobi' really crank me up because i also give my self stupidesc names just as a inside joke. My latest stupidesc name is 'archiebald' that is my Arch Linux user. :D Great video, great tips!

great, thanks.

I do appreciate this, I knew the basics of Git, but this improves my understanding of this; thanks a lot!

What if you just clicked that create button.

Do you have courses in platforms like Udemy or others where one can get a certificate ?

main and feature branches are all we ever need

one of best tutorials I found🔥

I like how you can link commit messages with the tasks, so you don’t need to make them meaningful after this, everything will be in task

HELP

Awesome tutorial. This man explained everything in a very Calm and awesome way. Loved It!!

Useful Video

Bravo! Not only the action steps to complete certain actions, but "why" and an explanation of what actually happens when you do! Nicely done.

thank u mr skellington

This guy made me realize that small habits can save big times, thanks a lot freeCodeCamp for introducing him.

It's like listening to Christoph Waltz. Very slick

Thanks for taking the time to create this video. I enjoyed your explanation, but was very distracted by a clicking sound in the background whenever you speak. I'm not sure whether this is an artifact of your microphone or processing setup, or whether you're perhaps audibly clicking through notes or your presentation and the sound of your mouse buttons gets picked up. However, once you hear it (and are sensitive to it), it distracts from the content. Perhaps something to improve in your recording setup.

Git was made to make easier to REVERT our changes during work, but those "pros" say what git commits must be clean as baby butt. So we must use TWO gits? One for actual work and the other for "pure clean commits? Such an absurdity..
"Never combine changes in one commit" - what? How ot possible at all if any tiny change affects the whole project? Maybe if you work on "To do list" such approach is possible, don't know, never done any todos.

Love this video especially the pace of the video so much!

Maybe the most useful (intermediate/advanced) video on git/Github I've seen so far

Great topics to talk about. Thanks!

This was very helpful!

Thanks a lot

For sure the best video I watched on git! Thank you so much.

Thank you FCC team! Great job again! 🖖