Many major and even little projects use the "conventional commits" strategy, which states the structure of a commit as:
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
And more linters "require" you to oblige by these rules, but not the repo-visualizer: on every commit, it throws an error within any linter and system hooks that require your commits to be conventional.
While this is not a critical priority, it still would be good to have a commit of repo-visualizer be more in a conventional format or just implement a config to edit the commit's message.
Many major and even little projects use the "conventional commits" strategy, which states the structure of a commit as:
And more linters "require" you to oblige by these rules, but not the repo-visualizer: on every commit, it throws an error within any linter and system hooks that require your commits to be conventional.
While this is not a critical priority, it still would be good to have a commit of repo-visualizer be more in a conventional format or just implement a config to edit the commit's message.