Yes. It is compiled to Vim script using ELVM[1]. Though the author of Vim script backend of ELVM is me :) [1]: https://github.com/shinh/elvm
No. It is a C compiler compiled to Vim script. So it is actually a C compiler written in Vim script.
The first pitfall can be statically detected with actionlint https://github.com/rhysd/actionlint > oops.yaml:20:24: property "jobone" is not defined in object type {jobtwo: {outputs: {}; result: string}} [expression]
Seems that Google has no budget to pay their GCP instances
Yes. It is compiled to Vim script using ELVM[1]. Though the author of Vim script backend of ELVM is me :) [1]: https://github.com/shinh/elvm
No. It is a C compiler compiled to Vim script. So it is actually a C compiler written in Vim script.
The first pitfall can be statically detected with actionlint https://github.com/rhysd/actionlint > oops.yaml:20:24: property "jobone" is not defined in object type {jobtwo: {outputs: {}; result: string}} [expression]
Seems that Google has no budget to pay their GCP instances