You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
2024-12-24 19:34:15 [INFO] Linting GIT_COMMITLINT items...
Error: -24 19:34:16 [ERROR] Found errors when linting GIT_COMMITLINT. Exit code: 1.
2024-12-24 19:34:17 [INFO] Command output for GIT_COMMITLINT:
------
⧗ input: Repo visualizer: update diagram
✖ subject may not be empty [subject-empty]
✖ type may not be empty [type-empty]
✖ found 2 problems, 0 warnings
ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint
------
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.
The text was updated successfully, but these errors were encountered: