forcedotcom / forcedotcom/code-analyzer

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

Open
#1,965 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
240
Forks
52
Avg merge
1d 23h
Merged PRs (30d)
5

Description

### 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

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.