Skip to content
Conventional Commits Validation

ci: Add Conventional Commit Linter #12

Sign in to view logs

ci: Add Conventional Commit Linter

ci: Add Conventional Commit Linter #12

Triggered via pull request January 11, 2024 02:54
@arielvalentinarielvalentin
synchronize #800
arielvalentin:add-conventional-commit-linters
Status Failure
Total duration 25s
Artifacts –

conventional-commits.yaml

on: pull_request
Conventional Commits Validation
9s
Conventional Commits Validation
Fit to window
Zoom out
Zoom in

Annotations

5 errors
Conventional Commit Compliance
91ac47206343421aa3d54e52f0cd31c746dd8646: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 | Merge branch 'main' into add-conventional-commit-linters | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Conventional Commit Compliance
91ac47206343421aa3d54e52f0cd31c746dd8646:1:57: 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 | Merge branch 'main' into add-conventional-commit-linters | ~
Conventional Commit Compliance
f3ab9f9b620526564c1326687b384908ad60c85a: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
f3ab9f9b620526564c1326687b384908ad60c85a: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.