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]>
|
Can this PR be closed? |
|
@njjetha can you update the PR to the latest QC Preflight checks? @ndechesne @lumag and team, the individual checkers that don't make sense or cause issues can be disabled? If you prefer, we can submit a new PR. |
What is the point of switching to the new workflow if we disable significant parts of it?
Abandoning the previous review comments? Definitely not. |
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