Gotta love humans who just give thousands of dollars of knowledge for absolutely free. What a wonderful individual Thanks for this
TimeLine 1:10 What is git 1:30 What is version control 2:10 Terms to be learn in video 5:20 Git commands 7:05 sign up in github 11:32 using git in local machine 11:54 git install 12:48 getting code editor 13:30 inside vsCode 14:30 cloning through vsCOde 17:30 git commit command 18:15 git add command 19:15 commiting 20:20 git push command 20:30 SSH Keys 25:25 git push 30:21 Review workflow so far 31:40 Compare between github workflow and local git workflow 32:42 git branching 56:30 Have fun is not allowed 1:01:50 Forking in git 1:07:55 Ending
16:28 if you are having problem with using command "ls -la", make sure that you change your terminal into Bash first. To change your terminal, 1. Head to the upper right corner on terminal and press the drop-down menu. 2. Select "Git Bash" terminal. 3. Start using the command "ls -la" there.
When you said CD = Change Directory, I went into a time warp. I bought my first PC in 1984. It had a massive 10 meg hard drive! I knew absolutely nothing about computers. Didn't even know anyone who had one. The computer came with a thick three-ring binder with the title, DOS. I read and reread and reread the entire book until it started to make sense. (The first version of Windows didn't come out until 1985.) In 1985, I bought an early copy of Symantec's Q&A, a (non-Windows) word processor, flat file, and report generator, which relied heavily on keystroke combinations to get things done but was hinting at a graphical interface. I ran a non-profit for many years with Q&A and loved it, such an improvement from WordStar. So, now at 72-years-old, to see CD = Change Directory, I say to myself, "Hey, I can do this." Thanks for a good tutorial.
Gwen articulated this topic so well and was able to break it down into simple terms for a newbie like me. She also explained everything very clearly, showcasing her intelligence in simplifying complicated concepts with ease. I am very grateful to have stumbled upon this video.
What an amazing explanation, thank you so much for being so clear and concise! A tip for new learners like myself: This video is slightly dated. GitHub now refers to the primary branch as "main" and not "master". If you try to run these commands exactly like Gwen in the video, you'll run into errors. Remember: main ✔️ master ❌
Whole course was broken down into heading and sub-headings, spending time on important ones and you made sure the basics were clear to the students, viewers or learners like me. Thank You Gwen.
Here are git commands to remember:- 1. git status 2. git add .(for all) / git add <filename> 3. git commit -m "message" 4. git commit -am "message" 5. git push 6. git push -u origin <branchname> 7. git pull 8. git branch 9. git branch -d 10. git checkout -b <new_branchname> 11. git checkout branchname 12. git reset 13. git reset <filename> 14. git reset -HEAD 15. git reset -HEAD~1 (OR) git reset -HEAD~2 and so on... 16. git reset -hard <commit_code>
This is an excellent, detailed tutorial for Git and GitHub. It’s long, but easy to follow, not least because there is no distracting music, no annoying jingles or graphics and perhaps most helpful, the narration is measured and carefully modulated ... you quickly feel at home with the delivery, from someone who really knows their subject material.
Really love this git and github intro course, it really touches a lot of things. 1. How to create a repo locally through the CLI(Command Line Interface) or directly from GITHUB 2. git flow by using the most common commands: git add - git commit and git push/git pull, all of them with their corresponding explanation. What "origin", "remote" and "master" mean. 3. git branching: all the commands involve in that kind of operation as well as best practices. 4. git merging: when we use a "feature" branch and it's time to merge to the "master" branch -- PR (Pull Request) on the Github side 5. How to deal with "conflicts" when merging. 6. Undoing in git: undoing from the stage area versus undoing if we have committed once or several times. 7. Understanding how and why we fork a repo on github. Really awesome content, thank a lot for such a valuable content.
This tutorial is probably the best github tutorial any beginner online could make use of. The lecture was succinct and it passed the desired information to the viewers, not having to make things overly complicated, she explains it so well.
I don't usually leave comments for tutorials, but let me say, this one fit like a glove to my newbie needs. Thanks a lot!
she is the most fluent instructor that answered all my questions while i was watching... imma go to her channel and subscribe rn.
4 years after and this is still insightful. Thank you so much.
Thank you, Maybe some suggestions, - add the changes of github defaulting to "main" instead of master and the configs on it. - Setting up SSH keys(20:30) first must be earlier than the cloning through VS Code(14:30), so we can follow along
At some point I thought I was dumb for not gasping the concept of git and GitHub because I’ve watched over 5 courses which were paid but I was getting even more frustrated. But here you are making it all clear, now I have the ahaaaaaaaaa moment. I’m in love with your teaching methods, they make sense to me and now I can rewatch those other courses. Thank you very much!!!
At 21:43, One important note:: If you choose a new name instead of automatically generated location, you have to use that location name when adding configuration code to the [~/.ssh/config] file. Nice tutorial. Thank you.
I finally understand Git after this video. I’ve asked so many questions to friends and watched several “quick” YouTube tutorials and was still confused about Git. Your tutorial was excellent and I’m glad I sat through the whole hour of it. It was completely worth my time. Thanks!
For beginners like me, who might be feeling lost with commands not working in the VS code terminal, all these commands will work on Git Bash since it can interpret all UNIX commands and git ones, on the top of it, it will track the edits you separately perform on VS code. So feel free and just git bash through this course.
@FaradayAcademy