forcedotcom / forcedotcom/code-analyzer

[Feature Request] Add Input Variable To Control PR Review Behavior

Offen
#1,965 3 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Vorherrschende Sprache
TypeScript
Sterne
240
Forks
52
Ø Merge
1 T. 23 Std.
Gemergte PRs (30 T.)
5

Beschreibung

### Product Area

The “Run Salesforce Code Analyzer” GitHub Action

### Your Need or Problem

Currently, if I want to leverage the new `num-sev{X}-violations-in-changed-files` output variables I have to provide a github token with read access. Doing so leads to the action submitting a review for my PR.

I don't want the action to leave a review, I would simply like to know if there are violations in my changed files so that I can take actions against that in a following step. This is a pain point.

### Your Desired Solution

I would like some sort of input variable that lets me disable the code review. This should default to false to ensure that no existing workflows are broken. This would allow me to make use of the newly introduced `*in-chaged-files` output variables _without_ having a a review submitted via the action itself.

Something along the lines of:

```yaml
disableReview:
description: 'Prevents the action from submitting a review even if the github token is provided'
required: false
type: 'boolean'
default: 'false'
```

### Alternatives Considered

_No response_

### Additional Context (Screenshots, Files, etc)

_No response_

### Workaround

_No response_

### Urgency

Moderate

Beitragsleitfaden

Beitragsleitfaden öffnen

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.