Parenthesized optional scope in commit message structure #174

New Issue

GiteaMirror · 2026-02-17T11:51:33-06:00

GiteaMirror commented

2026-02-17 11:51:33 -06:00

Originally created by @MartinSandeCosta on GitHub (May 10, 2023).

Commit message should be structured as per doc:

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

While these brackets are correctly indicating that said scope is to be optionally included, the specification is missing the mandatory parentheses that should surround the scope (if it exists). Maybe it can be included as:

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

[optional body]

[optional footer(s)]

Originally created by @MartinSandeCosta on GitHub (May 10, 2023). Commit message should be structured as per [doc](https://github.com/conventional-commits/conventionalcommits.org/blob/master/content/v1.0.0/index.md#summary): ``` <type>[optional scope]: <description> [optional body] [optional footer(s)] ``` While these brackets are correctly indicating that said scope is to be optionally included, the specification is missing the mandatory parentheses that should surround the scope (if it exists). Maybe it can be included as: ``` <type>[(optional scope)]: <description> [optional body] [optional footer(s)] ```

GiteaMirror closed this issue

2026-02-17 11:51:33 -06:00

GiteaMirror commented

2026-02-17 11:51:35 -06:00

@mentalisttraceur commented on GitHub (Aug 26, 2023):

Duplicate with #473 (that one does not have a name that makes it obvious what it's about)

@mentalisttraceur commented on GitHub (Aug 26, 2023): Duplicate with #473 (that one does not have a name that makes it obvious what it's about)

GiteaMirror commented

2026-02-17 11:51:36 -06:00

@MartinSandeCosta commented on GitHub (Sep 1, 2023):

Duplicated by #473

@MartinSandeCosta commented on GitHub (Sep 1, 2023): Duplicated by #473