A lot of people claim that with JavaScript one can build everything. So this post outlines my work on my cross-platform desktop automation framework for node: nut.js
GitHub Actions workflows are triggered on events which are caused by certain activities on GitHub, e.g. a push to a repository or the creation of a new issue. However, GitHub may not be our only source of events to trigger a workflow, so let’s see how we can trigger a workflow via web hook.
Given the ability to customise the runtime environment, responsibility for providing and maintaining a proper environment shifts from IT-Ops towards developers. Fortunate enough, we can apply well-known methods to make this effort less tedious: automated tests and test-driven development (TDD).
Whenever we execute a script, most often we do not think about what happens behind the curtains of our runtime. However, piecing together the bits and pieces to find out what is going on is pretty interesting!