Testing via commit?

Question

git

There was a question, whether to use git for testing of functions on live.
For example, make var_dump and other very small changes that are needed to understand how live works.
One developer litters the repository like this

. I tried to ask why do this, if, if necessary, you can directly test it on the live.
The argument was very sharp:
You can buy a car and drive it with your family, or you can carry bricks.
For me - a car, a tool for everything, and not just for the family.
If there are no serious arguments, then I see no point in this conversation.
What arguments can be made?
except for aesthetic reasons

Answer 1

You can buy a microscope and hammer nails with it, but it is wise to understand its capabilities and use it for its intended purpose. If it is not obvious, then no arguments will help.
Once you realize that code change history can be a good ally in developing and understanding a project, the desire to treat commit changes as a feature of saving changes will disappear and there will be a steady desire to commit history.
When the code developer, and ideally the whole team, commits the history of changes, the following opportunities appear:

• Understanding what motivates the change, because the commit is tied to the issue number or contains a clear comment;
  
• Understanding how to add new functionality if the commits in the history are concentrated changes related to specific requirements;
  
• Having in our asset the above features and adding a couple of tricks of working with git (the same applies to other VCS), we get the real king of the project.