[actions] Skipped jobs are displayed as failed #10463

New Issue

GiteaMirror · 2025-11-02T09:08:07-06:00

GiteaMirror commented

2025-11-02 09:08:07 -06:00

Originally created by @denyskon on GitHub (Mar 20, 2023).

Description

I have a workflow file with three different jobs. The workflow is triggered by push and issue_comment events, and an if statement in the job definition decides which of the jobs gets executed by the github.event_name variable.

In the actions list (/actions?workflow=&state=closed) the action run is being displayed as successful.

When opening the log view, the skipped job is being displayed correctly, but the steps are being displayed as failed.

In the code view, the action is being displayed as failed, and in the tooltip, the skipped job is being displayed as failed.

Gitea Version

1.19.0

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

Using the official docker image

Database

SQLite

Originally created by @denyskon on GitHub (Mar 20, 2023). ### Description I have a workflow file with three different jobs. The workflow is triggered by `push` and `issue_comment` events, and an if statement in the job definition decides which of the jobs gets executed by the `github.event_name` variable. In the actions list (`/actions?workflow=&state=closed`) the action run is being displayed as successful. ![grafik](https://user-images.githubusercontent.com/47871822/226448754-eb5d9410-8f4b-4bec-a80d-4e29466ec5cb.png) When opening the log view, the skipped job is being displayed correctly, but the steps are being displayed as failed. ![grafik](https://user-images.githubusercontent.com/47871822/226448966-6403fc37-b563-4144-b32b-248c1ad62017.png) In the code view, the action is being displayed as failed, and in the tooltip, the skipped job is being displayed as failed. ![grafik](https://user-images.githubusercontent.com/47871822/226449614-3d4d386f-c373-459e-9cdf-ffa65d381fec.png) ### Gitea Version 1.19.0 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? Using the official docker image ### Database SQLite

GiteaMirror added the topic/gitea-actions type/bug labels 2025-11-02 09:08:07 -06:00

GiteaMirror closed this issue

2025-11-02 09:08:08 -06:00

GiteaMirror commented

2025-11-02 09:08:08 -06:00

@a1012112796 commented on GitHub (Mar 21, 2023):

that's because there are only five optional commit status now: "pending", "success", "error", "failure", and "warning"

@a1012112796 commented on GitHub (Mar 21, 2023): that's because there are only five optional commit status now: "pending", "success", "error", "failure", and "warning"

GiteaMirror commented

2025-11-02 09:08:08 -06:00

@yardenshoham commented on GitHub (Mar 21, 2023):

I think GitHub keeps it on "pending" https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks#handling-skipped-but-required-checks

We could also add a new status? "skipped"

@yardenshoham commented on GitHub (Mar 21, 2023): I think GitHub keeps it on "pending" https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks#handling-skipped-but-required-checks We could also add a new status? "skipped"

GiteaMirror commented

2025-11-02 09:08:08 -06:00

@a1012112796 commented on GitHub (Mar 22, 2023):

Hmm, I think whether skipped means failed should be optional for each repo.

@a1012112796 commented on GitHub (Mar 22, 2023): Hmm, I think whether `skipped` means `failed` should be optional for each repo.

GiteaMirror commented

2025-11-02 09:08:09 -06:00

@denyskon commented on GitHub (Mar 22, 2023):

GitHub also seems to have neutral for that, at least that's what I have seen a few times.....

@denyskon commented on GitHub (Mar 22, 2023): GitHub also seems to have `neutral` for that, at least that's what I have seen a few times.....

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#10463