Level up with "Git Fundamentals"

Access all lessons in this tutorial.

No spam, unsubscribe at any time.

This is a free tutorial

In exchange for your email address, you'll get full access to this and other free Epic Web Dev tutorials.

Why? First and foremost, your inbox allows us to directly communicate about the latest Epic Web Dev material. This includes free tutorials, tips, and periodic update about trends, tools, and happenings in Web Development that I'm excited about.

In addition to the piles of free Epic Web Dev content, you'll get the earliest access and best discounts to the paid courses when they launch.

There won't be any spam, and every email you get will have an unsubscribe link.

If this sounds like a fair trade, let's go!

Current section: Commands 17 exercises

Git Fundamentals

Transcript

00:00 use git commit to make a commit commits require a message which we can use the dash m flag for i like to use present tense commit messages like add help init and status notes now instead of a

00:14 commit we actually got the status output here and that's because no files are staged to be committed we can fix that with git add dot which adds all those files and running our commit command again we see the branch it's abbreviated commit shaw and the message that we wrote three files were

00:32 changed with three insertions creating these three files and now when we run git status again we see that there's nothing to commit and we have a clean working tree

lesson

Understanding Git Commit, Add, and Status

The git commit command is used to make a commit. Commits require a message, which is added with the -m flag.

It's a good practice to use present tense commit messages:

git commit -m "Add help, init, and status notes"

After the commit command finishes, it will show the branch, its ab

Subscribe to unlock this lesson.

Transcript

00:00 use git commit to make a commit commits require a message which we can use the dash m flag for i like to use present tense commit messages like add help init and status notes now instead of a

00:32 changed with three insertions creating these three files and now when we run git status again we see that there's nothing to commit and we have a clean working tree

You might also like

Full Stack Vol 1

Kent C. Dodds

A comprehensive guide to full stack development

166 Interactive Exercises ・ Progress Tracking ・ Completion Certificate

Learn more