How to get the most value out of your git repository

As a beginner programmer, you can be surprised to see that people care so much about what goes into the git repository. Or worst, you can be wholly unaware & do your thing full of:

* fix the bug 
* another attempt 
* another attempt 2 
* another attempt 2
* finally!

while being judged on it from behind. I check repo history whenever there is a job applicant, and they share a GitHub profile or some example work. My main question is — do they already know to keep the repository neat, or it’s something we will have to work on when they join the team.

Why so much fuss?

There is a big difference between a git repository of a mature project and a repository created by an inexperienced developer. In a mature project, you can:

• find a reason to be of a given line while doing git blame
• write a changelog or release notes based on the git history alone
• revert some changes if necessary, with only the conflicts that couldn’t be avoided
• get the idea of what was merged by just seeing the git log

Those uses case appear days or weeks after you merged the changes. If history is a mess, you won’t get much of it anyway. As a beginner programmer working on a…