Skip to content
Ops - CodeQL

[Grug] Add DeepEP profiling named scopes #1793

Sign in to view logs

[Grug] Add DeepEP profiling named scopes

[Grug] Add DeepEP profiling named scopes #1793

Triggered via pull request June 4, 2026 20:51
@dlwhdlwh
opened #6175
codex/6139-deepep-trace-scopes
Status Success
Total duration 1m 35s
Artifacts –

ops-codeql.yaml

on: pull_request
Matrix: analyze
Fit to window
Zoom out
Zoom in

Annotations

4 errors
Analyze (javascript-typescript)
The `analysis-kinds` input is experimental and for GitHub-internal use only. Its behaviour may change at any time or be removed entirely. Specifying multiple values as input is no longer supported. Continuing with only `analysis-kinds: code-scanning`.
Analyze (javascript-typescript)
The `analysis-kinds` input is experimental and for GitHub-internal use only. Its behaviour may change at any time or be removed entirely. An analysis kind other than `code-scanning` was specified in a custom workflow. This is not supported and will become a fatal error in a future version of the CodeQL Action. If your intention is to use quality queries outside of Code Quality, use the `queries` input with `code-quality` instead.
Analyze (python)
The `analysis-kinds` input is experimental and for GitHub-internal use only. Its behaviour may change at any time or be removed entirely. Specifying multiple values as input is no longer supported. Continuing with only `analysis-kinds: code-scanning`.
Analyze (python)
The `analysis-kinds` input is experimental and for GitHub-internal use only. Its behaviour may change at any time or be removed entirely. An analysis kind other than `code-scanning` was specified in a custom workflow. This is not supported and will become a fatal error in a future version of the CodeQL Action. If your intention is to use quality queries outside of Code Quality, use the `queries` input with `code-quality` instead.