-
Notifications
You must be signed in to change notification settings - Fork 41
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
Implement Coding Standard Rules in CodeQL #98
Labels
Comments
ArielSAdamsNASA
pushed a commit
to ArielSAdamsNASA/to_lab
that referenced
this issue
May 21, 2021
ArielSAdamsNASA
pushed a commit
to ArielSAdamsNASA/to_lab
that referenced
this issue
May 21, 2021
ArielSAdamsNASA
pushed a commit
to ArielSAdamsNASA/to_lab
that referenced
this issue
May 26, 2021
ArielSAdamsNASA
pushed a commit
to ArielSAdamsNASA/to_lab
that referenced
this issue
May 26, 2021
ArielSAdamsNASA
pushed a commit
to ArielSAdamsNASA/to_lab
that referenced
this issue
May 26, 2021
astrogeco
added a commit
that referenced
this issue
Jun 10, 2021
…tandard-codeql Fix #98, Implement Coding Standard in CodeQL
astrogeco
added a commit
to nasa/cFS
that referenced
this issue
Jun 10, 2021
*Documentation Updates:* nasa/cFE#1598, Updated FS Read/WriteHeader API return documentation nasa/cFE#1601, Document CFE_ES_RunLoop increment task counter behavior nasa/cFE#1602, Document CFE_TBL_Unregister use-case nasa/cFE#1603, Update version description per current design *Standardize docs generation:* nasa/cFE#1615, standardize on "docs" subdirectory nasa/osal#1071, rename doc to docs nasa/PSP#294, rename doc to docs *Implement Coding Standard:* nasa/ci_lab#87 nasa/sample_app#149 nasa/sample_lib#63 nasa/sch_lab#79 nasa/to_lab#98 nasa/cFS-GroundSystem#180 nasa/elf2cfetbl#80 nasa/tblCRCTool#48 nasa/osal#1042 nasa/PSP#292
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
CodeQL does not use JPL rules, which is used in the upcoming coding standard.
Describe the solution you'd like
Implement JPL rules for CodeQL. Continue using the security queries, but keep them separate from the JPL results. Can use two different workflows, one for the coding standard and one for the security queries.
Describe alternatives you've considered
Might be able to use one workflow, as long as the results can be easily identified as a coding standard issue or security issue.
Additional context
JPL queries are found here: https://github.com/github/codeql/tree/main/cpp/ql/src/JPL_C
Requester Info
Ariel Adams, ASRC Federal
The text was updated successfully, but these errors were encountered: