The status of a workflow where no jobs had a matching condition (jobs.<job_id>.if) used to get a "skipped" status with a grey icon on the actions lists.
But some time within the last day that changed to a failed state with a red icon and a mail informing about the failed workflow.
The previous behaviour was much nicer. An error?
Same here. We have a Workflow running on the `deployment_status` event and we only care about the `success` state. This is causing quite a bit of noise as `pending` deployments are all showing as failures just because the `if` condition in the job doesn't pass.
We have reported the feedback to the appropriate engineering team for further investigation and evaluation. If have any progress, we will notify you in time.
Thank you, @BrightRan.
I just checked and the problem still exists.
Feel free to contact me if you need more info or examples.
Do we have any idea if this is an intentional change, or a bug? I've changed my workflow so that all the steps in the job have the if statement. This way I have a job with zero steps, rather than a workflow with zero jobs, and it achieves basically the same thing, but the workflow takes a couple of seconds longer.
We just "solved" by adding the condtional at each step in the job https://github.com/transcom/mymove/blob/master/.github/workflows/go-auto-approve.yml