Commit

After staging a file, we can commit it.

A commit is a snapshot of the repository at a given point in time. It's a way to save the state of the repository, and it's how Git keeps track of changes to the project. A commit comes with a message that describes the changes made in the commit.

Here's how to commit all of your staged files:

git commit -m "your message here"

Assignment

Commit the contents.md file with the message A: add contents.md.

You wouldn't normally start a commit message with A:, you'd just write the message, but we're going to use letters to help us easily identify commits in this course.

Run git status again, and you should see that the file is no longer staged.

Run and submit the CLI tests from inside the webflyx directory.

Tip

If you screw up a commit message, you can change it with the --amend flag. For example:

# Change the last commit message
git commit --amend -m "A: add contents.md"

The Boot.dev CLI requires you to be signed in to submit your solution!

Copy/paste one of the following commands into your terminal:

Run

bootdev run 321d7b2d-60b8-433c-9123-210bbf49c758

Submit

bootdev run 321d7b2d-60b8-433c-9123-210bbf49c758 -s

Run the CLI commands to test your solution.

git --no-pager log -n 1
- Expecting exit code: 0
- Expecting stdout to contain all of:
  - A:
  - add contents.md
  - commit

Using the Bootdev CLI

The Bootdev CLI is the only way to submit your solution for this type of lesson. We need to be able to run commands in your environment to verify your solution.

You can install it here. It's a Go program hosted on GitHub, so you'll need Go installed as well. Instructions are on the GitHub page.