[GH-ISSUE #473] Refine commit message format grammar #2141

New Issue

GiteaMirror · 2026-04-16T01:15:05-05:00

GiteaMirror commented

2026-04-16 01:15:05 -05:00

Originally created by @1e9y on GitHub (Sep 29, 2022).
Original GitHub issue: https://github.com/conventional-commits/conventionalcommits.org/issues/473

Current suggested format doesn't clearly state correct usage of optional scope. Commit header defined as following:

<type>[optional scope]: <description>

While later in text scope is defined as "contextual information and is contained within parenthesis". That means commit header should have following form:

<type>[(<scope>)]: <description>

Square brackets here means optional block. Parenthesis are literal symbols. <scope> is an arbitrary string.

Originally created by @1e9y on GitHub (Sep 29, 2022). Original GitHub issue: https://github.com/conventional-commits/conventionalcommits.org/issues/473 Current suggested format doesn't clearly state correct usage of optional scope. Commit header defined as following: ``` <type>[optional scope]: <description> ``` While later in text scope is defined as "contextual information and is _contained within parenthesis_". That means commit header should have following form: ``` <type>[(<scope>)]: <description> ``` Square brackets here means optional block. Parenthesis are literal symbols. `<scope>` is an arbitrary string.

GiteaMirror commented

2026-04-16 01:15:07 -05:00

@malware2101 commented on GitHub (Jan 10, 2025):

can you assign me this!!

@malware2101 commented on GitHub (Jan 10, 2025): can you assign me this!!

GiteaMirror commented

2026-04-16 01:15:07 -05:00

@bcoe commented on GitHub (Jan 15, 2025):

@malware2101 please go ahead and submit a PR 👍

@bcoe commented on GitHub (Jan 15, 2025): @malware2101 please go ahead and submit a PR 👍

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/conventionalcommits.org#2141