Inspect The History

Part of the Version Control section of Coddy's Terminal journey. Lesson 27 of 58.

The Cookbook repo now has a small but real history: an initial commit and a follow-up that adds a recipe.

Inspecting the history is the easiest way to confirm the work is in shape. You will print the commit count, the list of files that ended up in the latest commit, and confirm the build artifact stayed out of the repo.

Challenge

Beginner

Print the total number of commits using git rev-list --count HEAD.

Every run starts from a fresh copy of the folder, and the whole script in the editor runs again from the top. Nothing is committed for you: the editor starts with the commands of the previous steps (git init -q -b main, the git config lines and the two commits). Keep those lines in the editor. If you clear them you will see fatal: not a git repository.

Try it yourself

Terminal

git init -q -b main
git config user.name "Cookbook Dev"
git config user.email "dev@coddy.tech"
echo "*.log" > .gitignore
git add .
git commit -q -m "Initial site"
echo "# Pizza" > recipes/pizza.md
git add recipes/pizza.md
git commit -q -m "Add pizza recipe"
# Your commands below