Skip to content

Clang-tidy and include fix on libime/core #67

Clang-tidy and include fix on libime/core

Clang-tidy and include fix on libime/core #67

Triggered via push November 24, 2024 00:09
Status Success
Total duration 11m 30s
Artifacts

check.yml

on: push
Check clang-format
26s
Check clang-format
Matrix: Build and test
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
Build and test (gcc)
The following actions use a deprecated Node.js version and will be forced to run on node20: github/codeql-action/analyze@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Build and test (gcc)
Unable to validate code scanning workflow: error: getWorkflow() failed: Error: Expected to find a code scanning workflow file at /__w/libime/libime/.github/workflows/check.yml, but no such file existed. This can happen if the currently running workflow checks out a branch that doesn't contain the corresponding workflow file.
Build and test (gcc)
CodeQL Action v2 will be deprecated on December 5th, 2024. Please update all occurrences of the CodeQL Action in your workflow files to v3. For more information, see https://github.blog/changelog/2024-01-12-code-scanning-deprecation-of-codeql-action-v2/
Build and test (clang)
The following actions use a deprecated Node.js version and will be forced to run on node20: github/codeql-action/analyze@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Build and test (clang)
CodeQL Action v2 will be deprecated on December 5th, 2024. Please update all occurrences of the CodeQL Action in your workflow files to v3. For more information, see https://github.blog/changelog/2024-01-12-code-scanning-deprecation-of-codeql-action-v2/
Build and test (clang)
Unable to validate code scanning workflow: error: getWorkflow() failed: Error: Expected to find a code scanning workflow file at /__w/libime/libime/.github/workflows/check.yml, but no such file existed. This can happen if the currently running workflow checks out a branch that doesn't contain the corresponding workflow file.