Do you keep a tidy Git commit history?

Commits form one of the core concepts in git. They are snapshots of your branch at a certain point, recording your code changes. When you create a new commit, you usually add a message that describes your code changes. The commit messages are the logs of your changes.

In multiple instances, I have encountered unclear commit messages. This was frustrating, not just because of my slight obsession with quality and tidiness but also because I needed to urgently understand what was going on in this change to fix a production bug. Has this change caused the bug? Should…

--

--

--

Software engineer (JS | REACT | Node | AWS | Test Automation)

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Few words on the 4th element of Simple Design

M1 Mac + Logitech Mouse + Logi Options

Chapter Structure Evolution of S1000D Starting with the Issue 1.9 and Finishing with the Issue 5.0

Have you covered *this* when testing C and C++ Software?

Clean CSS: How to Spring Clean your Project

Live to Lear302

Romantic Project — How to create the NetFlix logo animation in Flutter

Using AWS Lambda, CloudWatch and Secrets Manager to schedule secure hits of a service endpoint

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Ali Haydar

Ali Haydar

Software engineer (JS | REACT | Node | AWS | Test Automation)

More from Medium

SOLID Principle in OOD

ADR — What, When, How?

How to use the Spring Boot Starter dependency to implement a Camunda External Task Client

Two Ways to Attract and Keep Good Developers