---
title: "Discussion on \"Commit Like a Pro\" | Hashnode"
description: "Discussion on \"Commit Like a Pro\". Committing changes is one of the common things that many developers do sometimes in case of contribution. You stage your changes and commit them so they will be trackable in the history. But what about conventions? Any difference between a dirty comm..."
url: "https://hashnode.com/posts/commit-like-a-pro/626be9dab7dcabd258e74315"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Commit Like a Pro](https://blog.imsadra.dev/commit-like-a-pro?utm_source=hashnode&utm_medium=feed)

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

Apr 29, 2022 · 5 min read · blog.imsadra.dev  
Updated Aug 17, 2022  
Read the article

-   [#git](https://hashnode.com/tag/git)
-   [#github](https://hashnode.com/tag/github)
-   [#best-practices](https://hashnode.com/tag/best-practices)
-   [#version-control](https://hashnode.com/tag/version-control)

## Written by

[Sadra Yahyapour](https://hashnode.com/@lnxpy)

@lnxpy

  
[View profile](https://hashnode.com/@lnxpy)

Campus Expert at GitHub · Open-Source Contributor · Python Developer · ML Enthusiast

A passionate software developer who enjoys sharing his thoughts with others and learning from them vise versa!

## Responses 5

Markdown supported · ⌘↵ to post

[Marcus Chambers](https://hashnode.com/@mcham)

[Sep 3, 2022](https://hashnode.com/posts/commit-like-a-pro/626be9dab7dcabd258e74315/comment/63139544d49bb9d8c2f744e2)

That was so well-explained. Thanks.

[yun zheng](https://hashnode.com/@yumzheng)

[Jul 29, 2022](https://hashnode.com/posts/commit-like-a-pro/626be9dab7dcabd258e74315/comment/62e3b517d8bf69c9bde61470)

Nice.

[Asqar Karim](https://hashnode.com/@asrim)

[Jul 26, 2022](https://hashnode.com/posts/commit-like-a-pro/626be9dab7dcabd258e74315/comment/62dfa0808730728f62e8d8ff)

Nice article. Good tips.

[Terence Munro](https://hashnode.com/@terrymunro)

[May 1, 2022](https://hashnode.com/posts/commit-like-a-pro/626be9dab7dcabd258e74315/comment/626dfbe7a2d355d4df43fa95)

👍 Good article. If you haven't already come across it, `commitlint` helps with this kind of thing. It has the ability for the team to make up a convention and help them stick to it by use of pre-commit hooks.

[Sadra Yahyapour](https://hashnode.com/@lnxpy)

[May 1, 2022](https://hashnode.com/posts/commit-like-a-pro/626be9dab7dcabd258e74315/comment/626dfbe7a2d355d4df43fa95#reply-626e1b7a454011df6e86c42c)

Thanks Terence. You're right. It backs to conventions actually. Thanks for mentioning.

[Conor Sheehan](https://hashnode.com/@ConorSheehan1)

[Apr 29, 2022](https://hashnode.com/posts/commit-like-a-pro/626be9dab7dcabd258e74315/comment/626c4f51a2d355d4df43d20a)

Nice article! IMO it's worth noting most git platforms ([github](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue), [bitbucket](https://support.atlassian.com/bitbucket-cloud/docs/resolve-issues-automatically-when-users-push-code/), etc.) support closing issues with specific commit keywords and an issue reference. E.g. `fix infinite recursion bug, closes #111`

[Sadra Yahyapour](https://hashnode.com/@lnxpy)

[Apr 30, 2022](https://hashnode.com/posts/commit-like-a-pro/626be9dab7dcabd258e74315/comment/626c4f51a2d355d4df43d20a#reply-626cea3db7dcabd258e760c8)

Thanks Conor. That's absolutely worth mentioning. I just updated the article.
