… yeah, we just moved some stuff to Actions, and it's been rather disappointing as onboarding goes. While the YAML represents jobs as a DAG, it seems like Actio

… yeah, we just moved some stuff to Actions, and it's been rather disappointing as onboarding goes. While the YAML represents jobs as a DAG, it seems like Actions can't actually evaluate them as such, and it inserts dependencies where none exist, i.e., it inserts stalls in the pipeline. Action builds aren't cached, so they're slow. The default token can't be extended to allow cross-repository access, forcing you to write your own app that can. The jobs, not the workflow, is the CI status/result, so you can't branch protect on a workflow. (You have to just have a dummy job … but you can't have an empty job, no, it has to run `true`…)