I guess, every time I work with yaml pipelines I end up refactoring things out to “normal” programming languages, so all these yaml harness looks really weird and unnecessary. As for the current project state mostly I am building community, people who would like to use the tool somehow …
IMHO, generally speaking it’s not just a JS. The declarative approach has its toll we end up having a lot of configurations files instead of having (one or two) normal imperative script
> Then there’s the DevOps and Quality layer. We have roughly 20-30 files for GitHub Actions workflows (lint, test, build, deploy, semantic release), Husky hooks (pre-commit, commit-msg), and pull request templates.
3. Adding GH action integration should be easy , added this to my todo list
4. Yes on the top pipeline structure there is a bit of yaml - it’s only required to reference linear list of jobs - jobs themselves are written in general programming languages . Probably in the simplest form I can even drop this first level yaml … will see , but imho I bit of yaml to structure out the list of jobs is ok, it’s not ok to embed into it action code, shell scripts , etc - to have nightmare of code to maintain and extend … the very idea that dsci is about