fixup: kill_state + get_states instead of filter_states #66
dlongit-commit-message-style.yml
on: push
Check commit message style
2s
Annotations
1 error and 1 warning
|
Check commit message style
The message 2 is invalid:
* Expected the subject to start with a verb in imperative mood consisting of letters and possibly dashes in-between, but the subject was: "fixup: label state structs as non_exhaustive". Please re-write the subject so that it starts with a verb in imperative mood.
The original message was:
fixup: label state structs as non_exhaustive
The message 3 is invalid:
* Expected the subject to start with a verb in imperative mood consisting of letters and possibly dashes in-between, but the subject was: "fixup: lint". Please re-write the subject so that it starts with a verb in imperative mood.
The original message was:
fixup: lint
The message 4 is invalid:
* Expected the subject to start with a verb in imperative mood consisting of letters and possibly dashes in-between, but the subject was: "fixup: errors". Please re-write the subject so that it starts with a verb in imperative mood.
The original message was:
fixup: errors
The message 6 is invalid:
* Expected the subject to start with a verb in imperative mood consisting of letters and possibly dashes in-between, but the subject was: "fixup: kill_state + get_states instead of filter_states". Please re-write the subject so that it starts with a verb in imperative mood.
The original message was:
fixup: kill_state + get_states instead of filter_states
|
|
Check commit message style
The following actions uses Node.js version which is deprecated and will be forced to run on node20: gsactions/commit-message-checker@16fa2d5de096ae0d35626443bcd24f1e756cafee. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|