Return `exit-code` when `reporter` is invalid

Repository metrics

Stars

10 stars (10 stars)

PR merge metrics

PR metrics pending (PR metrics pending)

Description

<reporter> should be set to <sarif> or <checkstyle>
Error: Process completed with exit code 1.
Run if ((  == 0 ))
/home/runner/work/_temp/d4e0e34c-bf86-4484-a6e8-9993c[67](https://github.com/nulls/diktat/pull/3/checks#step:3:70)45502.sh: line 1: ((: == 0 : syntax error: operand expected (error token is "== 0 ")
/home/runner/work/_temp/d4e0e34c-bf86-4484-a6e8-9993c6745502.sh: line 14: ((: != 0 : syntax error: operand expected (error token is "!= 0 ")
/home/runner/work/_temp/d4e0e34c-bf86-4484-a6e8-9993c6745502.sh: line 21: ((: <= 1 : syntax error: operand expected (error token is "<= 1 ")
/home/runner/work/_temp/d4e0e34c-bf86-4484-a6e8-9993c6745502.sh: line 26: ((: != 1 : syntax error: operand expected (error token is "!= 1 ")
Error: Process completed with exit code 1.

Contributor guide

Research direction

Examine the action's main entry point and ensure that when the reporter is invalid, the process exits with a non zero exit code. Look for where the error is printed and add process.exit(1) after that.

Tech stack

typescriptjavascriptnodejs

Domain

ci cd

Issue type

Bug

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

2

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

1-3 hours

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

Fresh

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

Clear

Prerequisites

GitGitHub Actions

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

75