Skip to content

Commit

Permalink
docs: add note to self about focusing on why and not what in commit m…
Browse files Browse the repository at this point in the history
…essages
  • Loading branch information
signekb committed Nov 14, 2023
1 parent dc195b9 commit 6424c22
Showing 1 changed file with 2 additions and 0 deletions.
2 changes: 2 additions & 0 deletions entries/git-workflow-guidelines/commits.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,8 @@ date: last-modified

{{< include /includes/_wip.qmd >}}

**Focus more on why the change was made, not what.**

After you have created a new branch, you probably want to start implementing some changes to your repository. This work could be adding a new feature to your code, fixing a bug, updating the documentation, or something else.

In Git, you log the process of your work through *commits*, the "save points" within Git's version control. Git does not log these save points automatically as you modify files in your repository, so you need to choose at which stages you want to commit/log your changes.
Expand Down

0 comments on commit 6424c22

Please sign in to comment.