Max Held

tweet: https://twitter.com/maxheld/status/1164200347642019841

@jimhester this is something I really don't understand about the current GitHub Actions design. I first though that node.js was privileged to be the only thing allowed in containerless actions...

it appears as per the above commit that action images are no longer cached. Calling them with a tag from docker "manually" will probably still get the tag, but there's...

above commits confirm that images are no longer pulled from docker hub, unless `docker://` is explicitly given.

AFAIK, the old, HCL-based GitHub actions would pull, not build, images for GitHub actions from Docker Hub when action images would be pushed and tagged properly (via the actions action)....

this is now supported https://help.github.com/en/articles/events-that-trigger-workflows#pull-request-events-for-forked-repositories

probably depends on https://github.com/actions/checkout/issues/15

might be added via PR here https://github.com/actions/starter-workflows/tree/master/ci

https://github.com/actions/starter-workflows/issues/23

same as #103, but for C code. Clang format is here: https://clang.llvm.org/docs/ClangFormat.html