Committing changes is a common action that many developers do most of the time in case of contribution. You stage your changes and commit them so then they will be trackable in the history. But what about conventions? Any difference between a dirty c...

Hashnode is a community-driven platform for developers to share knowledge, ask questions, and connect with peers in the tech industry. Developers can learn about new technologies, programming languages, and software development methodologies, engaging in discussions, and networking with fellow developers to expand their knowledge and grow their careers in tech.

Hashnode

Committing changes is a common action that many developers do most of the time in case of contribution. You stage your changes and commit them so then they will be trackable in the history. In this article, we are going to talk about some common conventions and git commit best practices in order to make perfect commits.

Commit Like a Pro

Conventions are important no doubt, but emojis seems strange for me - having emojis you need to have kinda a map explaining what every emoji means

I understand the point regarding emoji but seen many creative and productive commit patterns using gitmoji (<a href="https://github.com/carloscuesta/gitmoji" target="_blank" rel="noopener nofollow">https://github.com/carloscuesta/gitmoji</a>).
There are lots of solutions to enforce clean commit rule that can leverage proper emoji for different types of commit that can organize your git history.

I have a doubt, squash commits after finished the task, that’s a good practice ?

Commit messages should be clear and concise and Sandra elaborates this really well in the article.