Skip to content
.github/workflows/yamllint_blue.yml

Bump github/codeql-action from 3.29.10 to 4.32.6 #832

Sign in to view logs

Bump github/codeql-action from 3.29.10 to 4.32.6

Bump github/codeql-action from 3.29.10 to 4.32.6 #832

Triggered via pull request March 6, 2026 12:13
@dependabotdependabot[bot]
opened #557
dependabot/github_actions/github/codeql-action-4.32.6
Status Success
Total duration 16s
Artifacts –

yamllint_blue.yml

on: pull_request
Lint Blue
13s
Lint Blue
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
Lint Blue: ./.azure-pipelines/azure-pipelines.yml#L324
324:13 [comments-indentation] comment not indented like content
Lint Blue: ./.azure-pipelines/azure-pipelines.yml#L314
314:13 [comments-indentation] comment not indented like content
Lint Blue: ./.azure-pipelines/azure-pipelines.yml#L219
219:13 [comments-indentation] comment not indented like content
Lint Blue: ./.azure-pipelines/azure-pipelines.yml#L209
209:13 [comments-indentation] comment not indented like content
Lint Blue: ./.azure-pipelines/azure-pipelines.yml#L180
180:13 [comments-indentation] comment not indented like content
Lint Blue: ./.github/mergify.yml#L3
3:1 [document-start] missing document start "---"
Lint Blue: ./changelogs/fragments/312-add-create_blueprint-package_version.yaml#L3
3:95 [comments] missing starting space in comment
Lint Blue: ./changelogs/fragments/312-add-create_blueprint-package_version.yaml#L3
3:94 [comments] too few spaces before comment: expected 2
Lint Blue: ./changelogs/fragments/313-edge-commit-should-update-existing-ostee-repo.yaml#L3
3:149 [comments] missing starting space in comment
Lint Blue: ./changelogs/fragments/313-edge-commit-should-update-existing-ostee-repo.yaml#L3
3:148 [comments] too few spaces before comment: expected 2