While we are focusing on writing codes and Building apps , we often push code without carring the commit messages and thats where the problem starts. In future ,when we try to access code or its meaning we get confused so, Writing meaningful commit messages can save a lot of time answering many “why?” and “how?” questions, and thus gives us more time in the day to do productive work.
Basically, when are using github there is need to communicate between team members and also for our future reference.Let’s say there’s a bug in the application which was not there before. To find out what caused the problem, reading the commit messages could be handy. The proper commit message can save a great deal of time finding the recent changes related to a bug.
If we fix a bug or add a feature we will probably completely forget about it a month or two later. It’s not a good idea to think that if it’s not clear for others, they can ask us about it. Instead, we should provide proper commit messages for people to use as a resource in their daily work.
Good commit messages can be written in many different styles.As many companies have their own way to write commits messages for their code.
The commit message may have certain qualities :A great format for writing commit messages can be different in each team for different companies . The most important aspect is to keep it simple and readable.