gh-actions is a real pain to use and the documentation doesnt really help; the problem with it is that theres so much of it, that trying to fix a single issue by referring to the docs, is like searching for the proberbial needle in a haystack. Also, its impossible to read a single page of documentation without getting re-directed and distracted by something else you should supposedly know. It would be better to have task orientated documentation or a setp of recipes to well known problems, rather than have a sea of completely overwhelming documentation and virtually impossible to navigate.
Try this: Essentials of automated application deployment with GitHub Actions and GitHub Pages
gh-actions is a real pain to use and the documentation doesnt really help; the problem with it is that theres so much of it, that trying to fix a single issue by referring to the docs, is like searching for the proberbial needle in a haystack. Also, its impossible to read a single page of documentation without getting re-directed and distracted by something else you should supposedly know. It would be better to have task orientated documentation or a setp of recipes to well known problems, rather than have a sea of completely overwhelming documentation and virtually impossible to navigate.
Try this: Essentials of automated application deployment with GitHub Actions and GitHub Pages