-
Notifications
You must be signed in to change notification settings - Fork 13
ci: replace Repolinter with centralized compliance checks #24
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?
Conversation
Please explain the reason for the changes as part of the git commit body message. |
27c5a6b
to
866d358
Compare
Substitute the repolinter workflow with a comprehensive set of compliance and security checks. Project-specific exclusions are supported for non-applicable validations. This update also introduces a centrally-managed reusable workflow to streamline ongoing maintenance and ensure consistency. Signed-off-by: Neeraj Jetha <[email protected]>
ff44cd6
to
acb9909
Compare
Updated the body for GitHub commit message. |
Thanks, can you wrap the commit message lines to avoid more than 80 columns per line? |
Resolved in bcdcf3b |
Substitute the repolinter workflow with a comprehensive set of compliance and security checks. Project-specific exclusions are supported for non-applicable validations. This update also introduces a centrally-managed reusable workflow to streamline ongoing maintenance and ensure consistency. Signed-off-by: Neeraj Jetha <[email protected]>
Summary
qcom-preflight-checks calls a reusable-workflow that runs a series of preflight checks on your proposed contribution.
For more info check https://github.com/qualcomm/qcom-actions/blob/main/README.md