Skip to content
pr-checks

fix: making sure spec.groups[].rules[].for attribute is always defined for alerts as this is required by RHOBS #48

Sign in to view logs

fix: making sure spec.groups[].rules[].for attribute is always defined for alerts as this is required by RHOBS

fix: making sure spec.groups[].rules[].for attribute is always defined for alerts as this is required by RHOBS #48

Triggered via pull request April 22, 2024 11:21
@Nikokolas3270Nikokolas3270
opened #16
Nikokolas3270:checking-for-keyword-for-alerts
Status Failure
Total duration 3m 45s
Artifacts –

pr-checks.yaml

on: pull_request
lint
12s
lint
build
3m 35s
build
Fit to window
Zoom out
Zoom in

Annotations

1 error and 2 warnings
lint
You have commit messages with errors ⧗ input: fix: making sure spec.groups[].rules[].for attribute is always defined for alerts as this is required by RHOBS ✖ header must not be longer than 100 characters, current length is 110 [header-max-length] ✖ found 1 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint
lint
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
build
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, docker/setup-qemu-action@v2, docker/setup-buildx-action@v2, docker/build-push-action@v4. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.