Skip to content

fix: schedule day always at event start #701

fix: schedule day always at event start

fix: schedule day always at event start #701

Triggered via pull request February 12, 2025 09:42
Status Failure
Total duration 1m 43s
Artifacts

style.yml

on: pull_request
Matrix: Code Quality
Fit to window
Zoom out
Zoom in

Annotations

1 error and 9 warnings
Code Quality (27.x, 1.17.x)
Process completed with exit code 1.
Code Quality (27.x, 1.17.x)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
Code Quality (27.x, 1.17.x)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
Code Quality (27.x, 1.17.x)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
Code Quality (27.x, 1.17.x)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
Code Quality (27.x, 1.17.x)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
Code Quality (27.x, 1.17.x)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
Code Quality (27.x, 1.17.x)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
Code Quality (27.x, 1.17.x)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
Code Quality (27.x, 1.17.x)
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it