[Feature Request] Add Input Variable To Control PR Review Behavior
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- github-actions, typescript
- Domain
- ci-cd
Research direction
Start by locating the GitHub Action's input definitions and the path that submits a pull-request review. Add coverage for the new optional input, its false default, and the case where violation outputs are still available without submitting a review; run the action's existing tests or workflow checks.
Written by the indexing model from the issue text.
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:
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
- Dominant language
- TypeScript
- Stars
- 240
- Forks
- 52
- Avg merge
- 9h 48m
- Merged PRs (30d)
- 3
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from forcedotcom/code-analyzer
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
forcedotcom/code-analyzer#2094 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
forcedotcom/code-analyzer#2093 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
forcedotcom/code-analyzer#2091 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
forcedotcom/code-analyzer#2090 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
forcedotcom/code-analyzer#2099 ·
All issues in forcedotcom/code-analyzer
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
bcgov/bc-wallet-mobile#4761 · 1 comment ·
-
external-issue to-triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
area-deployment area-integrations triage:bot-seen
Difficulty 2/5 Half a day Newbie friendliness 86/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
refactor
Difficulty 2/5 1-3 hours Newbie friendliness 84/100