21–30 of 179 posts
Earlier quoted context omitted.
You can't rely on people spotting the significance of such changes
Tests would have caught it = https://github.com/rhysd/actionlint injection check
YAML is a nightmare fuel spec. In its quest to make markup "human readable", it has created countless footguns. I honestly prefer XML at this point.
Better move as much of that as possible into your own scripts. And your scripts can be portable between forges, and even run locally!
YAML is a nightmare fuel spec. In its quest to make markup "human readable", it has created countless footguns. I honestly prefer XML at this point.
It’s find for actions and workflows as long as you do no interpolation and logic. Better move as much of that as possible into your own scripts. And your scripts can be portable between forges, and even run locally!
YAML is a nightmare fuel spec. In its quest to make markup "human readable", it has created countless footguns. I honestly prefer XML at this point.
Peer review of changes is still important.
Multi-model cross-review is important
Earlier quoted context omitted.
It’s find for actions and workflows as long as you do no interpolation and logic. Better move as much of that as possible into your own scripts. And your scripts can be portable between forges, and even run locally!
Assigning an env var to an empty variable (env: { myvar: ${{unsetfoo}} }) should trigger an error, not silently pass an empty string.
YAML is a nightmare fuel spec. In its quest to make markup "human readable", it has created countless footguns. I honestly prefer XML at this point.