Of those, "NO" is fixed, 0 causing octal is fixed, to me that SQL syntax doesn't look any worse than the low bar set by normal SQL, and the CI providers using different schemas doesn't really have anything to do with YAML.
So that leaves two complaints.
I'm not immediately offended by the clock thing, like I am by NO and octal, but I don't really have the right experience to say how bad it is.
And I was going to say it's bad that nesting escaped string is hard, and it's a shame when languages don't have better quoting mechanisms... then I remembered that YAML has block quotes with no need to escape inside, so that example is just wrong. And they even link later to the stackoverflow post talking about YAML block quotes.
There are problems with YAML but these examples are not good ones.
((By the way, I've seen that "There are 63 different ways to write multi-line strings in YAML" link before but only took the time to fully understand it just now, and that's a gross exaggeration that makes me question the author more than it reinforces their point.
There's a reason the original link says -5- -6- NINE (or 63*, depending on how you count).
Block quotes have 1 or 2 characters to say what to do with newlines, then might have a digit to indicate indentation. That's "60" of the "63". I suppose if it allowed multi-digit numbers there it would be "billions" of ways to write multi-line strings in YAML? That number isn't a real criticism.))
(Ok not really)
I remember being in the traffic management center in Tokyo for an arranged visit and thought the entire city had come to a halt but red was high throughput not stoppage.