Add shell (.sh) checking #13

Sign in to view logs

Triggered via pull request April 8, 2024 20:06

opened #21

warthog9:add-shell

Status Failure

Total duration 14s

Artifacts –

commisery.yml

on: pull_request

commit-message / commit-message

Annotations

5 errors

commit-message / commit-message

1 of the pull request's commits are not valid Conventional Commits

(Commit 4075c2f5) Add shell (.sh) checking This more or less matches python, and should be fine for just about all shells that make use of '.sh' (typically) as a file extension should work on .sh files. Signed-off-by: John 'Warthog9' Hawley <jhawley@tenstorrent.com>

[C001] Type tag should be in lower case

(Commit 4075c2f5) Add shell (.sh) checking This more or less matches python, and should be fine for just about all shells that make use of '.sh' (typically) as a file extension should work on .sh files. Signed-off-by: John 'Warthog9' Hawley <jhawley@tenstorrent.com>

[C004] Subject should not contain an unknown tag type. Use one of: fix, feat, build, chore, ci, docs, perf, refactor, revert, style, test, improvement

(Commit 4075c2f5) Add shell (.sh) checking This more or less matches python, and should be fine for just about all shells that make use of '.sh' (typically) as a file extension should work on .sh files. Signed-off-by: John 'Warthog9' Hawley <jhawley@tenstorrent.com>

[C005] Zero spaces before and only one space allowed after the ":" separator

(Commit 4075c2f5) Add shell (.sh) checking This more or less matches python, and should be fine for just about all shells that make use of '.sh' (typically) as a file extension should work on .sh files. Signed-off-by: John 'Warthog9' Hawley <jhawley@tenstorrent.com>

[C008] Subject requires a separator (": ") after the type tag