Does it make sense to enable QC Preflight Checks and Stale workflow?

[mynameistechno]

Hi all,

Does it make sense to include the QC Preflight Checks at all on this repo? AFAIK this repo is developed internally, so perhaps not. But running semgrep seems like a useful check to run internally perhaps?

Having said that, we believe the Stale Issues/PR workflow would be useful to include here: https://github.com/qualcomm/qualcomm-repository-template/blob/main/.github/workflows/stale-issues.yaml

We're recommending teams set this workflow up so they receive notifications in case they miss a PR or issue. If we submit a PR, would you be able to merge it or otherwise get it included for the next push?

Thanks,
Mark

[shivrawa]

Hi @mynameistechno

1. Preflight Checks and other thing are handled internally during Pre-AU.
2. Integration team members will check about the semgrep and the stale issues workflow. @ssadhula will check.
3. As of now we don't accept any PR in KGSL. If some PR or Issues are raised, dev team will work on them internally and merge the code changes.

Regards,
Shivam

[mynameistechno]

We need to make it clear that PRs are not accepted in the README and/or contributing.md file; there should be guidance that explains the contribution policy, And perhaps you should leverage a GitHub Action/workflow to automatically respond to PR/Issues on relevant branches with a message.

[shivrawa]

Hi @mynameistechno sure, this makes sense to mention it somewhere about PR acceptance. We will work on this request.

For GitHub workflow the integration team will check, @ssadhula.

@ksanadhy let's take this up in next discussion.