Skip to content

feat: make config.trigger optional as it is not really required #7

feat: make config.trigger optional as it is not really required

feat: make config.trigger optional as it is not really required #7

Triggered via pull request November 16, 2023 07:46
@yeliexyeliex
opened #113
Status Failure
Total duration 13s
Artifacts

pr.yml

on: pull_request_target
Validate PR title
3s
Validate PR title
Fit to window
Zoom out
Zoom in

Annotations

1 error and 2 warnings
Validate PR title
No release type found in pull request title "make `config.trigger` optional as it is not really required". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/ Available types: - fix - feat - perf - docs - refactor - chore
Validate PR title
The following actions uses node12 which is deprecated and will be forced to run on node16: amannn/action-semantic-pull-request@v4. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Validate PR 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/