Skip to content

Add CodeQL MISRA/CERT C++ analysis workflow#102

Draft
RSingh1511 wants to merge 2 commits intoeclipse-score:mainfrom
RSingh1511:rs/codeql
Draft

Add CodeQL MISRA/CERT C++ analysis workflow#102
RSingh1511 wants to merge 2 commits intoeclipse-score:mainfrom
RSingh1511:rs/codeql

Conversation

@RSingh1511
Copy link
Copy Markdown
Contributor

Notes for Reviewer

Pre-Review Checklist for the PR Author

  • PR title is short, expressive and meaningful
  • Commits are properly organized
  • Relevant issues are linked in the References section
  • Tests are conducted
  • Unit tests are added

Checklist for the PR Reviewer

  • Commits are properly organized and messages are according to the guideline
  • Unit tests have been written for new behavior
  • Public API is documented
  • PR title describes the changes

Post-review Checklist for the PR Author

  • All open points are addressed and tracked via issues

References

Closes #

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Apr 29, 2026

License Check Results

🚀 The license check job ran with the Bazel command:

bazel run --lockfile_mode=error //:license-check

Status: ⚠️ Needs Review

Click to expand output
[License Check Output]
Extracting Bazel installation...
Starting local Bazel server (8.3.0) and connecting to it...
INFO: Invocation ID: 529e8676-1e8d-4af0-8a64-fb31a9781cd5
Computing main repo mapping: 
WARNING: For repository 'rules_python', the root module requires module version rules_python@1.4.1, but got rules_python@1.8.3 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
WARNING: For repository 'bazel_skylib', the root module requires module version bazel_skylib@1.7.1, but got bazel_skylib@1.9.0 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
WARNING: For repository 'rules_cc', the root module requires module version rules_cc@0.1.1, but got rules_cc@0.2.17 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
WARNING: For repository 'aspect_rules_lint', the root module requires module version aspect_rules_lint@1.0.3, but got aspect_rules_lint@2.3.0 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
WARNING: For repository 'buildifier_prebuilt', the root module requires module version buildifier_prebuilt@7.3.1, but got buildifier_prebuilt@8.5.1 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
WARNING: For repository 'score_tooling', the root module requires module version score_tooling@1.1.2, but got score_tooling@1.2.0 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
WARNING: For repository 'score_rust_policies', the root module requires module version score_rust_policies@0.0.3, but got score_rust_policies@0.0.5 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
WARNING: For repository 'score_crates', the root module requires module version score_crates@0.0.6, but got score_crates@0.0.9 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
WARNING: For repository 'googletest', the root module requires module version googletest@1.17.0.bcr.1, but got googletest@1.17.0.bcr.2 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
WARNING: For repository 'rapidjson', the root module requires module version rapidjson@1.1.0, but got rapidjson@1.1.0.bcr.20241007 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
Computing main repo mapping: 
Loading: 
Loading: 4 packages loaded
Loading: 4 packages loaded
    currently loading: 
WARNING: Target pattern parsing failed.
ERROR: Skipping '//:license-check': no such target '//:license-check': target 'license-check' not declared in package '' defined by /home/runner/work/logging/logging/BUILD
ERROR: no such target '//:license-check': target 'license-check' not declared in package '' defined by /home/runner/work/logging/logging/BUILD
INFO: Elapsed time: 5.448s
INFO: 0 processes.
ERROR: Build did NOT complete successfully
ERROR: Build failed. Not running target

@github-actions
Copy link
Copy Markdown

The created documentation from the pull request is available at: docu-html

@github-advanced-security
Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

@RSingh1511 RSingh1511 requested a deployment to workflow-approval May 4, 2026 07:52 — with GitHub Actions Waiting
@RSingh1511 RSingh1511 requested a deployment to workflow-approval May 4, 2026 07:52 — with GitHub Actions Waiting
@RSingh1511 RSingh1511 requested a deployment to workflow-approval May 4, 2026 08:07 — with GitHub Actions Waiting
@RSingh1511 RSingh1511 requested a deployment to workflow-approval May 4, 2026 08:07 — with GitHub Actions Waiting
@RSingh1511 RSingh1511 requested a deployment to workflow-approval May 4, 2026 11:50 — with GitHub Actions Waiting
@RSingh1511 RSingh1511 requested a deployment to workflow-approval May 4, 2026 12:58 — with GitHub Actions Waiting
@RSingh1511 RSingh1511 requested a deployment to workflow-approval May 4, 2026 12:58 — with GitHub Actions Waiting
@RSingh1511 RSingh1511 requested a deployment to workflow-approval May 4, 2026 13:02 — with GitHub Actions Waiting
@RSingh1511 RSingh1511 requested a deployment to workflow-approval May 4, 2026 13:02 — with GitHub Actions Waiting
@RSingh1511 RSingh1511 requested a deployment to workflow-approval May 4, 2026 13:14 — with GitHub Actions Waiting
@RSingh1511 RSingh1511 requested a deployment to workflow-approval May 4, 2026 13:14 — with GitHub Actions Waiting
@RSingh1511 RSingh1511 requested a deployment to workflow-approval May 4, 2026 13:30 — with GitHub Actions Waiting
@RSingh1511 RSingh1511 requested a deployment to workflow-approval May 4, 2026 13:30 — with GitHub Actions Waiting
@RSingh1511 RSingh1511 requested a deployment to workflow-approval May 5, 2026 05:43 — with GitHub Actions Waiting
@RSingh1511 RSingh1511 requested a deployment to workflow-approval May 5, 2026 05:43 — with GitHub Actions Waiting
@RSingh1511 RSingh1511 requested a deployment to workflow-approval May 5, 2026 09:17 — with GitHub Actions Waiting
@RSingh1511 RSingh1511 requested a deployment to workflow-approval May 5, 2026 09:17 — with GitHub Actions Waiting
@RSingh1511 RSingh1511 requested a deployment to workflow-approval May 5, 2026 10:41 — with GitHub Actions Waiting
@RSingh1511 RSingh1511 requested a deployment to workflow-approval May 5, 2026 10:41 — with GitHub Actions Waiting
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants