Skip to content

feat: Add renderName option #161

feat: Add renderName option

feat: Add renderName option #161

Triggered via pull request November 30, 2024 16:21
@micheljungmicheljung
opened #140
Status Failure
Total duration 12s
Artifacts

semantic-pull-request.yaml

on: pull_request_target
validate_title
3s
validate_title
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 warning
validate_title
No release type found in pull request title "WIP Add renderName option". 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
validate_title
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/