Skip to content

Create qcom-preflight-checks.yaml #144

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.

Sign up for GitHub

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

Open
Sandhya1236 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Create qcom-preflight-checks.yaml #144

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 24 additions & 0 deletions .github/workflows/qcom-preflight-checks.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,24 @@
name: QC Preflight Checks

on:
pull_request:
push:
branches: [main]
workflow_dispatch:

jobs:
preflight:
name: Run QC Preflight Checks
uses: qualcomm/qcom-reusable-workflows/.github/workflows/reusable-qcom-preflight-checks-orchestrator.yml@v2
with:
enable-semgrep-scan: true
Copy link
Copy Markdown
Contributor

@quic-viskuma quic-viskuma Apr 6, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

need to disable semgrep scan for Kernel

Copy link
Copy Markdown

@mynameistechno mynameistechno Apr 6, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@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.

enable-dependency-review: true
enable-repolinter-check: true
enable-copyright-license-check: true
enable-commit-email-check: true
enable-commit-msg-check: false
enable-armor-checkers: false

permissions:
contents: read
security-events: write
1 change: 1 addition & 0 deletions README
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,3 +7,4 @@ needs.

There is also a ci.conf.sample file if you want to create your own
configuration file for local integration testing.
For license information, see the ./LICENSE file.
Loading