Skip to content

feat(topic): are branches actually getting versioned this is a breaki… #82

feat(topic): are branches actually getting versioned this is a breaki…

feat(topic): are branches actually getting versioned this is a breaki… #82

Triggered via push April 9, 2025 09:07
Status Failure
Total duration 17s
Artifacts

dev.yml

on: push
Enforce Branch Name Convention
3s
Enforce Branch Name Convention
commitlint
12s
commitlint
gitguardian-scan
12s
gitguardian-scan
Unit-Tests
2s
Unit-Tests
E2E-Tests
3s
E2E-Tests
generate-dev-semantic-version
0s
generate-dev-semantic-version
build-bcl-dev-package-and-publish
0s
build-bcl-dev-package-and-publish
Make-Blazor-Wiki-Artifact-Trigger-GH-Pages-In-BlazorWasmTest
0s
Make-Blazor-Wiki-Artifact-Trigger-GH-Pages-In-BlazorWasmTest
Fit to window
Zoom out
Zoom in

Annotations

1 error
commitlint
You have commit messages with errors ⧗ input: feat(topic): are branches actually getting versioned this is a breaking change BREAKING CHANGE: Major version please ✖ header must not be longer than 72 characters, current length is 78 [header-max-length] ✖ found 1 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint