Skip to content
CodeQL

Watchfolders should start scan just after startScans call, not after a wait period #572

Sign in to view logs

Watchfolders should start scan just after startScans call, not after a wait period

Watchfolders should start scan just after startScans call, not after a wait period #572

Triggered via pull request August 29, 2024 08:59
@hdsdi3ghdsdi3g
opened #176
issue175
Status Success
Total duration 6m 32s
Artifacts –

codeql-analysis.yml

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

Annotations

2 warnings
Analyze (java)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, github/codeql-action/init@v2, actions/setup-java@v3, 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/
Analyze (java)
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/