@Findus23 I've added a Linter instead of adding a test with symfony. Tried the problem we had before and it's correctly marked as error. See 780b749
Guess that should be enough to prevent further problems like this, right?

Not sure how helpful error messages like this are:

======================
= Linting YAML files =
======================
Error: syntax error: expected <block end>, but found '<block sequence start>' (syntax)
Error: Process completed with exit code 1.

@sgiehl Is it possible to make a more detailed error reports in YAML Lint?

Interestingly running yamllint regexes/**/*.yml locally gives nice error messages.

➜  ~/public_html/device-detector git:(ymllint) ✗ yamllint regexes/**/*.yml
regexes/device/mobiles.yml
  17576:5   error    syntax error: expected <block end>, but found '<block sequence start>' (syntax)

I see now that it shows an inline block in https://github.com/matomo-org/device-detector/pull/6434/files#diff-1c8c04e817f8cf3650ade17a6d2a3080093d82d90fc1ecd8e2919e1f74c0e88fR17576, but only after uncollapsing the mobiles.yml section.

And one has to look at https://github.com/matomo-org/device-detector/actions/runs/374180337 instead of https://github.com/matomo-org/device-detector/actions/runs/374180337 to see the nice overview of errors.

as @Findus23 mentioned. The errors should be highlighted in the diff on github. Guess there's not much that can be changed on the error messages. But imho that should be enough... we should at least now see if any yml file is broken