Peter Bittner

@keleshev Any opinion on this?

@nerdoc Did you ever start with the tests? Did you also plan to add a CI setup? If it helps, I could add something like this as a test infrastructure:...

Docker's [Best practices for writing Dockerfiles](https://docs.docker.com/develop/develop-images/dockerfile_best-practices/#user) recommend using a non-root user in the Dockerfile. If I'm not mistaken that's what #1485 was trying to get fixed. As a (temporary) workaround...

> ``` > npm ERR! A complete log of this run can be found in: > npm ERR! /home/runner/.npm/_logs/2023-02-19T09_21_52_696Z-debug.log > ``` Is `runner` maybe already the unprivileged user we want...

I agree on reporting errors in a user-friendly manner. The syntax, as shown off by your example, might be good to revise, though. `=` seems to work out better than...

> By updating our parser, we may be able to both `:` and `=` and migrate to `=` eventually in the future. That sounds promising. Lets proceed with that. :rocket:

@dmarinuswoodwing I opened #532 as a dedicated issue for the non-working examples.

The failing of the `CI / lint` job is likely unrelated to the changes introduced in this PR. – Go error: `undefined: any`

This would be a nice enhancement of the Git aliases. Please, merge!

> @bittner Could you `rebase` or `amend`, then `push`? The CI runs are too old to re-run. Done. CI jobs all pass. Ready for merging?