Adapt the specification to Git's official terminology and recommendations #172

Open
opened 2026-02-17 11:51:27 -06:00 by GiteaMirror · 0 comments
Owner

Originally created by @TristanCottam on GitHub (Apr 15, 2023).

I noticed that Git's documentation about git commit itself recommends limiting the commit "description" length to "less than 50 character[s]" (which I dare rather interpret as "50 characters or less" — it doesn't mention anything about the 72-character "body" rule), as well as using the term "title" instead of "description" and "description" instead of "body".

In a nutshell, I think the specification should be more strict and explicit, basing itself on Git's official documentation, dare I say even being more opinionated at times (while not being part of the official documentation, a soft limit on the commit description's line length should be specified), in order to achieve further standardization.

Originally created by @TristanCottam on GitHub (Apr 15, 2023). I noticed that [Git's documentation about `git commit`](https://git-scm.com/docs/git-commit) itself recommends limiting the commit "description" length to "less than 50 character[s]" (which I dare rather interpret as "50 characters or less" — it doesn't mention anything about the 72-character "body" rule), as well as using the term "title" instead of "description" and "description" instead of "body". In a nutshell, I think the specification should be more strict and explicit, basing itself on Git's official documentation, dare I say even being more opinionated at times (while not being part of the official documentation, a soft limit on the commit description's line length should be specified), in order to achieve further standardization.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/conventionalcommits.org#172