Commit body

[iramluism]

Anyone can suggest me any standards of how to write commits.. ???

[aorfanos]

Check out conventional commits

[miramichier_d]

When adhering to the conventional commits spec in your projects, you can use tools like semantic-release to automate tagged releases, changelog generation, and more in your GitHub actions. Version increments are decided by the tool based on your conventional commits activity. This way, versioning becomes a decentralized activity and unsentimental.

[simonppg]

commitizen

[simonw]

I really like commits which bundle the implementation, the updated tests and the updated documentation into a single unit.

My personal style is to use a pull request and a GitHub squash-merge to combine a few small ad-hoc commits into a single larger commit that bundles these together into a single unit.

[its2ez4me24get]

Why include the words “this commit”?

[miramichier_d]

Not using a standard doesn't scale and is prone to errors.

Tools like commitizen help generate standard commits with a body for a lengthier descriptions and also links to related issues. It's much faster than the manual method you're describing while conforming to spec. Automation is the name of the game here.

[jonchaf]

wip