Adrien Vergé

TL;DR: For those seeking a quick-win to silent the error on GitHub Actions, here are 4 solutions: \- use [config option](https://yamllint.readthedocs.io/en/stable/rules.html#module-yamllint.rules.truthy) `rules: {truthy: {check-keys: false}}` \- use [config option](https://yamllint.readthedocs.io/en/stable/rules.html#module-yamllint.rules.truthy) `rules:...

> Is this going in at some point? Not that I'm aware of. Do you want to implement it?

Hello, I still think that using regular expessions is the option that gives the most flexibility (as opposed to options that allow ignoring comments based on prefixes only, which may...

Hello, I get your point :+1: But still, I feel that future users could want to allow some comments that don't start a line (e.g. `- yaml line #noqa`). If...

Hello, thanks for contributing to yamllint! I just posted my opinion on this rule idea: https://github.com/adrienverge/yamllint/issues/454#issuecomment-1460609614. (In any case a contribution of this type would need more tests, including different...

Hello, Currently there isn't any yamllint rule that enforce such a notation. Your "key-value pairs" example can be generalized with other types of data, which would give: ```yaml -   name:...

I guess the simplest implementation would answer "yes"? What do you think?

Hello, This seems normal behavior to me. I don't think this is related to anchors, you can remove `&list` from your example and you would get the same results. The...

Hello, thanks for the report! I guess the bug comes from PyYAML (the YAML parser behind yamllint) not converting `5319E7` (nor `5319e7`) to a float, while according to [the YAML...

@perlpunk thanks! It's clearer now why PyYAML doesn't convert `5319e7` to a float. My point of view: - There remains a problem with yamllint, because @andreineculau's first code snippet makes...