mirror of
https://github.com/conventional-commits/conventionalcommits.org.git
synced 2026-03-22 12:44:37 -05:00
Does Conventional care if the description is capitalized or not? #72
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/conventionalcommits.org#72
Reference in New Issue
Block a user
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?
Originally created by @epage on GitHub (Aug 14, 2019).
The current spec does not say one way or the other but all the examples are lower case and someone tells me Angular's spec required it.
@damianopetrungaro commented on GitHub (Aug 15, 2019):
Het @epage this is what we recommend :D
https://www.conventionalcommits.org/en/v1.0.0-beta.4/#are-the-types-in-the-commit-title-uppercase-or-lowercase
@epage commented on GitHub (Aug 15, 2019):
that is about the type while I'm talking about the description after the colon.
@JeanMertz commented on GitHub (Aug 17, 2019):
I guess that someone was me? 😉
In either case, it's mentioned here in the Angular CONTRIBUTING.md file:
@bcoe commented on GitHub (Aug 20, 2019):
I tend towards lower-case, but not a hill I think is worth dying on; by which I mean, I don't think it's necessarily worth adding more complexity to the spec enforcing my pedantry.
@bcoe commented on GitHub (Sep 7, 2019):
👍 we call out in the specification that conventional commits are not case sensitive.
@denisw commented on GitHub (Dec 18, 2023):
Sorry to comment on such an old ticket, but as mentioned in an earlier comment, the spec only calls this out for the commit type, but not the description. It would still be helpful to tweak the first FAQ entry so that this is explicit, as I just stumbled over this point myself (it's what led me to this issue in the first place).