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
Hi! Dsci tool author here. Thanks for attention .
1. The post is written by me, not generated by AI
2. It’s better to browse documentation from http://deadsimpleci.sparrowhub.io/doc/README that way all links should work , sorry for confusion
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
5. For people curious to play with there is forgejo public instance already set with dsci - http://deadsimpleci.sparrowhub.io/doc/demo
what is this vibeslop?
none of the links work
[dead]
The first section in the introduction describes a YAML file. Bait and switch?
(I added Show HN to your title because that's the convention for sharing your work on HN - see https://news.ycombinator.com/showhn.html)
Links to Forgejo and CI are broken in the README. I wanted to fix them, but I'm not even sure where the [~ci] link should lead.
All links are fixed now
thanks!