Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
feat: add JUnit reporter for unit tests and upload test results #192
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Uh oh!
There was an error while loading. Please reload this page.
feat: add JUnit reporter for unit tests and upload test results #192
Changes from all commits
b2b46376ed1bde0e79aee1abd028d3ed652dd8b4ed70764eaFile filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
Check warning on line 231 in .github/workflows/frontend-pr-workflow-v1.yml
Move this write permission from workflow level to job level.
Check failure on line 267 in .github/workflows/frontend-pr-workflow-v1.yml
inputs.lint-command is vulnerable to script injection: values of inputs are provided by whoever triggers the workflow. Change this workflow to not use user-controlled data directly in a run block, for example by assigning this expression to an environment variable.
Check failure on line 321 in .github/workflows/frontend-pr-workflow-v1.yml
inputs.pre-test-command is vulnerable to script injection: values of inputs are provided by whoever triggers the workflow. Change this workflow to not use user-controlled data directly in a run block, for example by assigning this expression to an environment variable.
Check failure on line 365 in .github/workflows/frontend-pr-workflow-v1.yml
inputs.pre-test-command is vulnerable to script injection: values of inputs are provided by whoever triggers the workflow. Change this workflow to not use user-controlled data directly in a run block, for example by assigning this expression to an environment variable.
Check failure on line 380 in .github/workflows/frontend-pr-workflow-v1.yml
inputs.integration-test-command is vulnerable to script injection: values of inputs are provided by whoever triggers the workflow. Change this workflow to not use user-controlled data directly in a run block, for example by assigning this expression to an environment variable.
Check failure on line 525 in .github/workflows/frontend-pr-workflow-v1.yml
inputs.pre-test-command is vulnerable to script injection: values of inputs are provided by whoever triggers the workflow. Change this workflow to not use user-controlled data directly in a run block, for example by assigning this expression to an environment variable.
Check failure on line 582 in .github/workflows/frontend-pr-workflow-v1.yml
inputs.pre-test-command is vulnerable to script injection: values of inputs are provided by whoever triggers the workflow. Change this workflow to not use user-controlled data directly in a run block, for example by assigning this expression to an environment variable.
Check warning on line 254 in .github/workflows/frontend-pr-workflow-v2.yml
Move this write permission from workflow level to job level.
Check warning on line 255 in .github/workflows/frontend-pr-workflow-v2.yml
Move this read permission from workflow level to job level.
Check failure on line 291 in .github/workflows/frontend-pr-workflow-v2.yml
inputs.lint-command is vulnerable to script injection: values of inputs are provided by whoever triggers the workflow. Change this workflow to not use user-controlled data directly in a run block, for example by assigning this expression to an environment variable.
Check failure on line 294 in .github/workflows/frontend-pr-workflow-v2.yml
inputs.clean-command is vulnerable to script injection: values of inputs are provided by whoever triggers the workflow. Change this workflow to not use user-controlled data directly in a run block, for example by assigning this expression to an environment variable.
Check failure on line 297 in .github/workflows/frontend-pr-workflow-v2.yml
inputs.build-command is vulnerable to script injection: values of inputs are provided by whoever triggers the workflow. Change this workflow to not use user-controlled data directly in a run block, for example by assigning this expression to an environment variable.
Check failure on line 349 in .github/workflows/frontend-pr-workflow-v2.yml
inputs.pre-test-command is vulnerable to script injection: values of inputs are provided by whoever triggers the workflow. Change this workflow to not use user-controlled data directly in a run block, for example by assigning this expression to an environment variable.
Check failure on line 354 in .github/workflows/frontend-pr-workflow-v2.yml
inputs.unit-test-command is vulnerable to script injection: values of inputs are provided by whoever triggers the workflow. Change this workflow to not use user-controlled data directly in a run block, for example by assigning this expression to an environment variable.
Check failure on line 408 in .github/workflows/frontend-pr-workflow-v2.yml
inputs.integration-test-command is vulnerable to script injection: values of inputs are provided by whoever triggers the workflow. Change this workflow to not use user-controlled data directly in a run block, for example by assigning this expression to an environment variable.
Check failure on line 462 in .github/workflows/frontend-pr-workflow-v2.yml
inputs.deploy-command is vulnerable to script injection: values of inputs are provided by whoever triggers the workflow. Change this workflow to not use user-controlled data directly in a run block, for example by assigning this expression to an environment variable.
Check notice
Code scanning / SonarCloud
Write permissions should be defined at the job level Low
Check failure on line 390 in .github/workflows/frontend-pr-workflow.yml
inputs.unit-test-command is vulnerable to script injection: values of inputs are provided by whoever triggers the workflow. Change this workflow to not use user-controlled data directly in a run block, for example by assigning this expression to an environment variable.
Check failure
Code scanning / SonarCloud
GitHub Actions should not be vulnerable to script injections High