NOTICE: All new Git repositories on GitHub will be named "main" instead of "master" starting October 1, 2020 as part of the company’s effort to remove unnecessary references to slavery and replace them with more inclusive terms.
Until you understand the concepts upon which Git is built, you’ll feel like a stranger in a foreign land., Tom Preston-Werner, author of
The Git Parable
"The following parable will take you on a journey through the creation of a Git-like system from the ground up. Understanding the concepts presented here will be the most valuable thing you can do to prepare yourself to harness the full power of Git.
The concepts themselves are quite simple, but allow for an amazing wealth of functionality to spring into existence. Read this parable all the way through and you should have very little trouble mastering the various Git commands and wielding the awesome power that Git makes available to you."
Download and read the The Git Parable
Reading time: 30 to 60 minutes.
Take a 5 to 10 minute break before diving into the next video, as you will not only be learning about the basics of Git and version control, but you will also be practicing these concepts on your own Git repository.
Although the video duration is close to 15 minutes, this session will probably take more than 1 hour (or even more), since you will be practicing along with
We suggest that you run the commands through the intergrated terminal of VSCode. (Tip: Press Ctrl+J to open/close the terminal while in VSCode)
Duration: 16 minutes
This section contains helpful links to other content. It isn’t required, but you should consider it supplemental if you need to dive deeper into
Read Chapter 1.1 through 1.4 in this book about version control to learn the differences between local, centralized, and distributed version control systems.
- Reading time: 15 to 30 minutes
Watch this video about how Git can improve the workflow of both an individual and a team of developers.
- Duration: 6 minutes
This section contains questions for you to check your understanding of this lesson. If you’re having trouble answering the questions below on your own, clicking the small arrow to the left of the question will reveal the answers.
What kind of program is Git?
- Git is a version control program.
What are the differences between Git and a text editor in terms of what they save and their record keeping?
- A text editor can only make and save changes to a file.
- Git tracks changes to the files and their contents over time.
Does Git work at a local or remote level?
- Git works on a local level. Any changes you make are saved locally with Git.
Does GitHub work at a local or remote level?
- GitHub works on a remote level. You must push your local changes (using Git) to Github.
Why is Git useful for an individual developer?
- Git is useful for creating snapshots of your work. If you realize halfway through that you’ve messed up, it’s much easier to reset.
Why are Git and GitHub useful for a team of developers?
- Git and GitHub are useful for teams because they can merge code together. A developer can work on one part of the code while a second developer works on another part. They can then use Git and GitHub to easily combine their changes.
LOOKING FOR HELP?
When looking for help, try doing so in the following order:
- Did you try everything you could?
- Did you read the documentation?
- Did you Google for it?
- Did you post your question on Slack/Forum?
- Did you ask your fellow students for help?
- Did you ask your Mentors for help?
- Did you leave a comment on the comments section of this page?
- Did you ask your Instructor for help?