-
I’m trying to avoid one job to run conditionnally. For instance, let’s say I want to control a “/rebase” command to only trigger the rebase job steps on PR:
The issue is that the workflow will exit in error (and so, send failure emails). In the Action UI, clicking on it will redirect to the previous running workflow of another type. One workaround right now is to let the job starting, and duplicate the condition on each step:
Is there any way to completely prevent the job to start, and thus, avoiding the cirrus-actions/rebase@1.2 docker image action build? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
Hi @didrocks , In the past, if all jobs in a workflow were skipped with the conditions, the workflow will display as “skipped/no status” status with a grey icon. But now, it displays as failed status. I had reported this issue to the appropriate engineering team, and the team has began to investigate it. |
Beta Was this translation helpful? Give feedback.
-
What is the status on this? Is it by design or a bug? |
Beta Was this translation helpful? Give feedback.
Hi @didrocks ,
In the past, if all jobs in a workflow were skipped with the conditions, the workflow will display as “skipped/no status” status with a grey icon. But now, it displays as failed status.
I had reported this issue to the appropriate engineering team, and the team has began to investigate it.
Currently, we don’t have any other ways to skip the jobs. However, as a workaround, you can add a job to always run in the workflow, you do not need to add any usable steps in this job, and just execute a line of script that don’t make sense. At this situation, when all other jobs are skipped with the if condition, the workflow will not be failed status.