A commit message describes the changes saved in a version-control commit. Git requires one when `git commit` records the files prepared with `git add`. section 2.3.3
Write a message as part of the incremental tracking workflow:
- Make changes, check whether unrelated files should remain untracked, and update `.gitignore` when needed. section 2.3.3
- Prepare the selected files with `git add`, then save them with `git commit -m "my message about these changes"`. section 2.3.3
- Review messages with `git log` to understand what happened at each point in the repository history. section 2.3.5
Initial project commit
After staging the Python project files, create a descriptive snapshot with `git commit -m "Initial python project commit"`. Later, inspect its history with `git log` and examine its file changes with `git show <commit-id>`. section 2.3.3 section 2.3.5
git commit -m "Initial python project commit"
See the complete initial-commit command used after staging the Python project. section 2.3.3
