ci: Add Conventional Commit Linter #15
arielvalentinconventional-commits.yaml
on: pull_request
Conventional Commits Validation
4s
Annotations
5 errors
|
Conventional Commit Compliance
ac4d03e42a7335b28b44f022b2b8fb1f2a5e583f:1:1: error: Commits MUST be prefixed with a type, which consists of a noun, feat, fix, etc., followed by the OPTIONAL scope, OPTIONAL !, and REQUIRED terminal colon and space.
1 | Update conventional-commits.yaml
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
Conventional Commit Compliance
ac4d03e42a7335b28b44f022b2b8fb1f2a5e583f:1:33: error: Commits MUST be prefixed with a type, which consists of a noun, feat, fix, etc., followed by the OPTIONAL scope, OPTIONAL !, and REQUIRED terminal colon and space.
1 | Update conventional-commits.yaml
| ~
|
|
Conventional Commit Compliance
48075b145cad4cfa68e4b61d6a8de4b40e6472f0:1:1: error: Commits MUST be prefixed with a type, which consists of a noun, feat, fix, etc., followed by the OPTIONAL scope, OPTIONAL !, and REQUIRED terminal colon and space.
1 | Update conventional-commits.yaml
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
Conventional Commit Compliance
48075b145cad4cfa68e4b61d6a8de4b40e6472f0:1:33: error: Commits MUST be prefixed with a type, which consists of a noun, feat, fix, etc., followed by the OPTIONAL scope, OPTIONAL !, and REQUIRED terminal colon and space.
1 | Update conventional-commits.yaml
| ~
|
|
Conventional Commits Validation
❌ Found 4 Conventional Commit compliance issues, and 0 warnings.
|