No, see my example again - there is a newline after the bar. I think it is important to the YAML parser.
If you have a command comprising of more than one line in Unix/Linux, every newline you put in has to have a backslash at the end, except the last one. It signifies to the parser than another line is to come.
I get another error:
# Unable to parse YAML
# while scanning a simple key
# in ‘string’, line 54, column 11:
# command:|
# ^
# could not find expected ‘:’
# in ‘string’, line 62, column 1:
# jobs:
When i try to validate i get an error:
can not read a block mapping entry; a multiline key may not be an implicit key at line 56, column 131: … /${site_name}/wp-content/themes/ ^
So, I gave two things to try, and explained both of them twice, and the second one has still not been applied. Worth a try, d’ya reckon? Backslashes (\)…
Just on the lines that make up the command (five in your case, since you do not want to put a line continuation on the last one, since there is not continuation on the last one, by definition).
I will be doing you a huge disservice if I make the fix for you, since the only way to learn is to apply what you read. Do also search for “line continuation bash Linux” in your favourite search engine, if you wish.
I mentioned the command you are getting stuck on. You put it in this thread! It has five lines plus one:
I am signing off for the evening. I wish you the best of luck