Foundations: Update the description of what a good commit message explains #29001
Labels
Status: Stale
This issue/PR has been inactive for over 30 days and will be closed if inactivity continues
Checks
Describe your suggestion
In the Commit Messages lesson, it's mentioned twice that a commit message should describe both the problem a change solves and how it solves it. I believe the 'how' part may be unnecessary.
The article How to Write a Git Commit Message, listed in the assignment section, emphasizes that commit messages should focus on why a change is made, not how, as the code itself shows how the problem is solved. I agree with this point.
Let me know if you agree that the relevant sections of the lesson should be updated.
Path
Foundations
Lesson Url
https://www.theodinproject.com/lessons/foundations-commit-messages
(Optional) Discord Name
Maddie
(Optional) Additional Comments
No response
The text was updated successfully, but these errors were encountered: