Skip to content

Feat/define shared notification models #248

Feat/define shared notification models

Feat/define shared notification models #248

Triggered via pull request November 7, 2025 09:56
Status Failure
Total duration 1m 11s
Artifacts

main.yaml

on: pull_request
semantic_pull_request  /  build
6s
semantic_pull_request / build
build  /  build
1m 7s
build / build
Fit to window
Zoom out
Zoom in

Annotations

1 error
semantic_pull_request / build
No release type found in pull request title "Feat/define shared notification models". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/ Available types: - feat: A new feature - fix: A bug fix - docs: Documentation only changes - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc) - refactor: A code change that neither fixes a bug nor adds a feature - perf: A code change that improves performance - test: Adding missing tests or correcting existing tests - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm) - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs) - chore: Other changes that don't modify src or test files - revert: Reverts a previous commit