---
title: "Comment by KOTP on \"Gits and GitHub: The Fundamentals\" | Hashnode"
description: "To make a commit we&#39;ll use the git commit -m &quot;your_commit message &quot; command. Instead, prefer using git commit -v if you are not using git commit -"
url: "https://hashnode.com/posts/gits-and-github-the-fundamentals/62c84e7f55f37390f97c9ef7/comment/62cb22a6bffc4694f5bc5564"
---

[Discussion](https://hashnode.com/posts/gits-and-github-the-fundamentals/62c84e7f55f37390f97c9ef7)

Comment [Gits and GitHub: The Fundamentals](https://hashnode.com/posts/gits-and-github-the-fundamentals/62c84e7f55f37390f97c9ef7)

[KOTP](https://hashnode.com/@KOTP)

[Jul 10, 2022](https://hashnode.com/posts/gits-and-github-the-fundamentals/62c84e7f55f37390f97c9ef7/comment/62cb22a6bffc4694f5bc5564)

> To make a commit we'll use the git commit -m "your\_commit_message_" command.

Instead, prefer using `git commit -v` if you are not using `git commit -p` (perhaps also with `-v`) to force a pause to think about the story you want to write from the view of your git log. Using `git commit -m` encourages less thoughtful history being written.

Use the editor coming up, and the diff presented to remind you why the changes are committed in this commit, in this one snapshot.
