Create qcom-preflight-checks.yaml#144
Create qcom-preflight-checks.yaml#144Sandhya1236 wants to merge 1 commit intoqualcomm-linux:mainfrom
Conversation
744690b to
8969a32
Compare
|
@Sandhya1236 can you address the issue Repolinter found? If you click on the failed check and expand the repolinter output you can see the one Failing error is the readme is not referencing the license file
|
a21f353 to
d37a1e1
Compare
This PR adds the Qualcomm QC Preflight Checks workflow using the shared orchestrator: qcom-reusable-workflows/reusable-qcom-preflight-checks-orchestrator.yml@v2 The workflow enables: - Semgrep scan - Dependency review - Repolinter check - Copyright/license check - Commit email check These checks help standardize code quality and security validation across the repository. Signed-off-by: Sandhya Adavikolanu <sadaviko@qti.qualcomm.com>
d37a1e1 to
34b7f4a
Compare
| name: Run QC Preflight Checks | ||
| uses: qualcomm/qcom-reusable-workflows/.github/workflows/reusable-qcom-preflight-checks-orchestrator.yml@v2 | ||
| with: | ||
| enable-semgrep-scan: true |
There was a problem hiding this comment.
need to disable semgrep scan for Kernel
There was a problem hiding this comment.
@quic-viskuma but isn't this particular workflow going to run on this kernel-config repo? I.e. PRs to kernel-config will trigger this workflows based on the file path. Or do we also use the workflow files defined here in Coral CI + kernel?
For kernel, I don't think any of the below checks make sense. So, I think we should enable this workflow only for kernel-config itself, but for kernel we prob don't want to run any of these as they are meant for QC-authored projects, not upstream projects with their own guidelines.

This PR adds the Qualcomm QC Preflight Checks workflow using the shared orchestrator: qcom-reusable-workflows/reusable-qcom-preflight-checks-orchestrator.yml@v2
The workflow enables:
These checks help standardize code quality and security validation across the repository.