Skip to content

fix: only notify change when kube config exists, isnt empty and complete (#190) #252

fix: only notify change when kube config exists, isnt empty and complete (#190)

fix: only notify change when kube config exists, isnt empty and complete (#190) #252

Triggered via pull request July 26, 2023 11:34
@adietishadietish
synchronize #192
Status Failure
Total duration 24s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

conventionalCheck.yml

on: pull_request_target
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 warning
main
No release type found in pull request title "only notify change when kube config exists, isnt empty and complete (#190)". Add a prefix to indicate what kind of release this pull request corresponds to (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
main
The following actions uses node12 which is deprecated and will be forced to run on node16: amannn/action-semantic-pull-request@d2ab30dcffc66150340abb5b947d518a3c3ce9cb. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/