Hi @ravgeetdhillon, many thanks for sharing this super-useful GitHub action with us!
On the job.status, it looks like "skipped" status has been missed out as a potential option. "skipped" is a valid, documented result/conclusion for both jobs and steps contexts so it'd be really appreciated if it could be captured similar to "cancelled".
It might seem odd, but I leverage notify-slack-action@v2 as the last in a chain of jobs which outputs their overall status like shown below. So that how's we can potentially end up with the "skipped" status needing to notify Slack.
Hi @ravgeetdhillon, many thanks for sharing this super-useful GitHub action with us!
On the
job.status
, it looks like "skipped" status has been missed out as a potential option. "skipped" is a valid, documented result/conclusion for bothjobs
andsteps
contexts so it'd be really appreciated if it could be captured similar to "cancelled".It might seem odd, but I leverage notify-slack-action@v2 as the last in a chain of jobs which outputs their overall status like shown below. So that how's we can potentially end up with the "skipped" status needing to notify Slack.
Cheers, Rishav