-
Notifications
You must be signed in to change notification settings - Fork 54
Open
Labels
USER STORYNew feature or requestNew feature or request
Description
Product Area
The "Run Salesforce Code Analyzer" GitHub Action
Your Need or Problem
Currently there is an option to have a quality gate on all the issues using this method:
- name: Check the Outputs to Determine Whether to Fail
if: |
steps.run-code-analyzer.outputs.exit-code > 0 ||
steps.run-code-analyzer.outputs.num-sev1-violations > 0 ||
steps.run-code-analyzer.outputs.num-sev2-violations > 0 ||
steps.run-code-analyzer.outputs.num-violations > 10
run: exit 1
Your Desired Solution
It would be good if there would also be an possibility to have a quality gate on the changed files:
- name: Check the Outputs to Determine Whether to Fail
if: |
steps.run-code-analyzer.outputs.changedFiles.exit-code > 0 ||
steps.run-code-analyzer.outputs.changedFiles.num-sev1-violations > 0 ||
steps.run-code-analyzer.outputs.changedFiles.num-sev2-violations > 0 ||
steps.run-code-analyzer.outputs.changedFiles.num-violations > 10
run: exit 1
This way it would be possible to improve quality over time as you might have some legacy code which already may have issues
Alternatives Considered
No response
Additional Context (Screenshots, Files, etc)
No response
Workaround
No response
Urgency
Low
Metadata
Metadata
Assignees
Labels
USER STORYNew feature or requestNew feature or request