@lee-dohm wrote: It sounds like you're confusing the concepts of "workflow" and "action". A workflow consists of multiple actions that can depend on one another or run independently. So if you want something to happen after something else, they should probably be two actions in the same workflow. Now, an action that depends on another action will not be executed if the depended upon action fails, but because actions are so open-ended I'm not sure what it is that you need to do on failure that couldn't be accomplised within the action. Example requirements: Build the code If code fails to build, send an email to Dev If code successfully built, run tests Email test report to QA For this, I would create one workflow consisting of two actions: Build the code, send email to Dev on failure Test code, email test report to QA Would something like that work for your envisioned use case? There are cases that at the end of a workflow, no matter if it has completed successfully or if it has failed, we need to execute certain tasks. Or we might need to execute some tasks if any of the workflow steps have failed. The CI/CD tools I have used in the past all support this functionality. See https://jenkins.io/doc/book/pipeline/syntax/#post for an example in Jenkins.
... View more
With GitHub Actions we can implement complete CI/CD workflows. But is there a way to display test, code coverage, and miscellaneous reports in a friendly HTML format like Jenkins and other CI/CD platforms? Or is it recommended to offload testing to another platform (e.g. Jenkins, Circle CI, etc.)? What about artifact management?
... View more