Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Failure doesn't show as failure

Open
#2,691 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
github-actions
Domain
ci-cd, security

Research direction

Start with the upload-sarif step in a workflow triggered by merge_group, reproducing removal of the merge queue item and observing the following conditional step. Compare the reported failure with the displayed status of the Publish step. Done means establishing whether upload-sarif or the GitHub Actions UI owns the mismatch and identifying the required behavior.

Written by the indexing model from the issue text.

Description

We have a step that uses upload-sarif. It ran on merge_group: but failed because the merge queue item was removed from the queue. This resulted in the following error message (which seems normal, branch is deleted by removal from queue):

Image

Notice that somehow the step is still shown as successful, and yet the step failed because the next step had a condition to run if it failed. I'm wondering if there's something missing from the upload-sarif to make the "Publish" step red cross too, or this is maybe a GHA UI glitch.

Dominant language
TypeScript
Stars
1.6k
Forks
493
Avg merge
1d 13h
Merged PRs (30d)
44

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/codeql-action

All issues in github/codeql-action

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.