Brian
Brian
@someone42 Pinging to check in on a possible followup to this PR?
@jameswalmsley Pinging to check in on a possible followup to this PR?
Hi again--to update, previously, we raised PRs https://github.com/gozfree/gear-lib/pull/90, https://github.com/gozfree/gear-lib/pull/91, https://github.com/gozfree/gear-lib/pull/93, https://github.com/gozfree/gear-lib/pull/94, https://github.com/gozfree/gear-lib/pull/95, and https://github.com/gozfree/gear-lib/pull/96 for bugs found with CodeQL, which were merged. **We believe this is conclusive evidence that CodeQL...
@gozfree Pinging to check in on a possible followup to this PR?
@100 Pinging to check in on a possible followup to this PR?
This workflow streamlines filtering out rules (perhaps for false positives); uploads the CodeQL results as an artifact, and uploads the CodeQL results to the repository under the Security tab and...
@MightyPork We configured CodeQL for various open-source embedded repos independently, and we are trying to see what developers' hesitations, if any, are with incorporating static analysis tools into their testing....
Thanks for your comments. If you'd like to add some steps from this CodeQL workflow (like uploading to Code scanning alerts under the Security tab, or the ability to filter...
I want to clarify that `fail_on_error.py` is a script that forces the step to fail if an error is found within the code (which in turn makes the entire workflow...
@no1wudi Pinging to check in on a possible followup to this PR?