I have always been a fan of GitHub Actions workflows but for some reason never liked YAML files as being the assigned file format for non-linear workflows. While YAMLs are great as configuration files, they can be quite tedious when it comes to creating, reviewing, and maintaining workflows.
To solve this, I created a visual node system that makes the workflow creation and maintenance process more efficient and intuitive. It's a straightforward node engine with an UI editor.
I have always been a fan of GitHub Actions workflows but for some reason never liked YAML files as being the assigned file format for non-linear workflows. While YAMLs are great as configuration files, they can be quite tedious when it comes to creating, reviewing, and maintaining workflows.
To solve this, I created a visual node system that makes the workflow creation and maintenance process more efficient and intuitive. It's a straightforward node engine with an UI editor.
Examples for such a node graph are here: https://www.actionforge.dev/github/actionforge/graph-runner/...
and here: https://www.actionforge.dev/github/actionforge/graph-editor/....
For clarification, they are directly executed on GitHub runners. These graphs took me minutes to build in order to focus on my actual project.
The next time you create a new repo, give it a try. Love to hear your thoughts!
Thanks!