github-starred/conventionalcommits.org
2
0
Fork 0
mirror of https://github.com/conventional-commits/conventionalcommits.org.git synced 2026-03-22 12:44:37 -05:00
Code Issues 153 Packages Projects Releases Wiki Activity

Letter case for description #91

New Issue
Closed
opened 2026-02-17 11:44:54 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-02-17 11:44:54 -06:00
Owner
Copy Link

Originally created by @mark-rushakoff on GitHub (Mar 11, 2020).

It looks like conventional commits do not explicitly specify whether a description should begin with an uppercase or lowercase letter, although all the examples appear to begin with a lowercase letter.

Could the next revision recommend that the description starts with a lowercase letter? Something like:

A description SHOULD begin with a lowercase letter, except when the first word would normally begin with an uppercase letter, such as a proper noun or acronym.

Originally created by @mark-rushakoff on GitHub (Mar 11, 2020). It looks like conventional commits do not explicitly specify whether a description should begin with an uppercase or lowercase letter, although all the examples appear to begin with a lowercase letter. Could the next revision recommend that the description starts with a lowercase letter? Something like: > A description SHOULD begin with a lowercase letter, except when the first word would normally begin with an uppercase letter, such as a proper noun or acronym.
GiteaMirror added the suggestion label 2026-02-17 11:44:54 -06:00
GiteaMirror commented 2026-02-17 11:44:57 -06:00
Author
Owner
Copy Link

@damianopetrungaro commented on GitHub (Mar 15, 2020):

IMHO there isn't a benefit of putting it on the specs itself.
But I'd 👍 a line saying "it is cool to use both, but try to be consistent if possible".
What do you think?

@damianopetrungaro commented on GitHub (Mar 15, 2020): IMHO there isn't a benefit of putting it on the specs itself. But I'd 👍 a line saying "it is cool to use both, but try to be consistent if possible". What do you think?
GiteaMirror commented 2026-02-17 11:44:58 -06:00
Author
Owner
Copy Link

@tunnckoCore commented on GitHub (Oct 3, 2020):

@damianopetrungaro agree.

@mark-rushakoff, also, this allows things like commitlint exist.

Close?

@tunnckoCore commented on GitHub (Oct 3, 2020): @damianopetrungaro agree. @mark-rushakoff, also, this allows things like `commitlint` exist. Close?
GiteaMirror commented 2026-02-17 11:44:59 -06:00
Author
Owner
Copy Link

@damianopetrungaro commented on GitHub (Oct 3, 2020):

Yup gonna close due to inactivity, if we see some demand for this we can add some info in the FAQ section!

@damianopetrungaro commented on GitHub (Oct 3, 2020): Yup gonna close due to inactivity, if we see some demand for this we can add some info in the FAQ section!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
discussion
enhancement
greenkeeper
help wanted
meeting-agenda
operations
process
pull-request
Mirrored from GitHub Pull Request
 question
suggestion
support
triaged
No Label suggestion
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/conventionalcommits.org#91
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?