Simple tips to make your local code reviews more effective.

Code is read much more often than it is written.¹ But what about commit messages?

Commit messages are written once and read infinitely more.

You never go back and change commit messages in your master branch, ideally, you don’t even have the option. Yet, the  Git commit history is one of the most important things in your project.

Your commit history is where you turn when you want to:

  • Learn about original requirements for the code you are changing
  • Check why a file was changed recently
  • Which one of the last merges broke your master branch

Of course, you can always visit your online repository managers, such as  GitHub or  GitLab. However, these tools make it cumbersome to check branching structure or glance at the evolution of a branch or a file.

#git #programming #software-development #terminal #code-review

Never Leave the Terminal with These Git Log Features
1.10 GEEK