The BEST way to learn Git👩‍💻 #technology #programming #software #career #code #tech #learncode

[ashtag]

You showed us the workflow in like 10 secs that's dope.

[JoshLathamTutorials]

I wish this was taught in schools. Too many junior devs struggle with this and it's literally the industry standard.

[BenRangel]

A good method of practical git learning is to have a friend set up a repo. You start a new branch that changes a file, then your friend changes the same file and pushes to master/main while you try to resume your branch.
Then you learn how to deal with the merge conflicts.
In a repo where it doesn't matter if you mess up.

But you pretty much need to try it out practically to get it - it's very hard to learn this from a textbook or documentation only.

[CodingWithLewis]

What would you like me to explain next? 🤔

[william.darrigo]

Git is difficult at first but once you learn it's really straightforward

[ethanboyd]

I'm taking the Odin Project Right now, the first things it teaches you are how to use the Command Line and how to use Git and Github!!

[XXXI]

Omg, thank you so so much Lewis. Git is so intimidating to me and all the tutorials look like they require a "minimum 3 years experience" with a billion ways of doing the exact same thing. This is so refreshing and encouraging.

[BenRangel]

When I learned git and github (coming from other version control systems) I was confused by the term "pull request". I knew what it was but I just felt it should be called "push request" or "merge request".
I viewed everything from the eyes of me as a contributor. I do 'git push' to update my branch, so I figured I'd call it something with push when I wanted to update someone else's main branch.

Someone had to explain to me a few times the term 'pull request' is seen from the eyes of the maintainer, as they are requested to pull changes into their repo.

(that being said, it's still not a perfect term in my eyes. Repo maintainers most often say "I'm gonna merge this", they don't really say "I'm gonna pull this")

[landonwjohnson]

In a previous role, we brought on several junior developers, leading to a day where I devoted eight hours solely to code review due to their unfamiliarity with Git. I ended up creating documentation on guide how they should be using Git within our project to streamline the process.

[ggff]

I basically create a repository, and test my code 2-3 times and push directly into master branch for personal project. Two step process

[crystalriddle]

I am sooo happy I found you! This will help tremendously. I am so lost in git, at this point I feel like I have messed up everything lol. Thank you for all of your helpful shorts and videos.

[identiticrisis]

This repository is such a wonderful idea, thank you for bringing it to my attention!

I've just started on my first proper coding project and decided I need to sit down and learn some discipline with version control.

[andrewmanninen]

This may help my team when we finally migrate from CVS to git

[randomname]

You don't open source your code because you want money.

I don't open source my code because it's way too embarrassing.

[FernandoHernandez-jpgt]

This makes so much sense now in a general way. Thank you!

[zyrenth]

Damn I'm watching your content for over 7 months now and I love it. Keep up the good work man.

[inferens]

I connected gitlab to vs code. I uploaded 3 little websites

[tahmidrahmankhan]

I've done a 'git' class in CS50 (Harvard university), they guys are awsome.

[nikoladedovic]

This is very powerfull, nowhere on the internet they were so concrete about what's actually "contributing to open source" means. You could actually ask GPT, BUT...

[rushas]

PS: you still can become a "programmer" without learning the Git.
It's just less painful to use a version control system