conventionalcommit indicator #16

New Issue

GiteaMirror · 2026-02-17T11:32:26-06:00

GiteaMirror commented

2026-02-17 11:32:26 -06:00

Originally created by @elypter on GitHub (Feb 10, 2018).

for machine readability and to differentiate normal commit messages from conventional commits i suggest that there should be one or more characters at the beginning of the line to indicate a conventional commit.

example:

$fix(gui):spelling error in settings wnidow

Originally created by @elypter on GitHub (Feb 10, 2018). for machine readability and to differentiate normal commit messages from conventional commits i suggest that there should be one or more characters at the beginning of the line to indicate a conventional commit. example: $fix(gui):spelling error in settings wnidow

GiteaMirror closed this issue

2026-02-17 11:32:27 -06:00

GiteaMirror commented

2026-02-17 11:32:28 -06:00

@stevemao commented on GitHub (Feb 11, 2018):

Can you elaborate?

@stevemao commented on GitHub (Feb 11, 2018): Can you elaborate?

GiteaMirror commented

2026-02-17 11:32:29 -06:00

@elypter commented on GitHub (Feb 12, 2018):

the point of a leading character is that it makes conventionalcommits easy to identify for tools and also for users. everyone who has seen one before immediately recognizes it and doesnt have to ponder if the commits just use a similar syntax by accident. it also helps to avoid conflicts if a commit of a project that doesnt support conventional commits just happens to have a commit with a valid syntax and if tools can identify conventional commit by a leading character it can also check for syntax errors. it also spreads the word if people visit a project with conventional commits and ask themselves what the meaning of the commit with same leading character mean and then got to the documentation or faq.

@elypter commented on GitHub (Feb 12, 2018): the point of a leading character is that it makes conventionalcommits easy to identify for tools and also for users. everyone who has seen one before immediately recognizes it and doesnt have to ponder if the commits just use a similar syntax by accident. it also helps to avoid conflicts if a commit of a project that doesnt support conventional commits just happens to have a commit with a valid syntax and if tools can identify conventional commit by a leading character it can also check for syntax errors. it also spreads the word if people visit a project with conventional commits and ask themselves what the meaning of the commit with same leading character mean and then got to the documentation or faq.

GiteaMirror commented

2026-02-17 11:32:30 -06:00

@stevemao commented on GitHub (Feb 12, 2018):

Which tools are you talking about specifically? Have you tried https://github.com/conventional-changelog/conventional-commits-detector?

@stevemao commented on GitHub (Feb 12, 2018): Which tools are you talking about specifically? Have you tried https://github.com/conventional-changelog/conventional-commits-detector?

GiteaMirror commented

2026-02-17 11:32:31 -06:00

@elypter commented on GitHub (Feb 13, 2018):

oh, i didnt know this tool. thanks

@elypter commented on GitHub (Feb 13, 2018): oh, i didnt know this tool. thanks

GiteaMirror commented

2026-02-17 11:32:32 -06:00

@stevemao commented on GitHub (Feb 13, 2018):

It's Ok :)

@stevemao commented on GitHub (Feb 13, 2018): It's Ok :)

GiteaMirror referenced this issue

2026-02-17 11:55:40 -06:00