Remove obsolete CodeQL setup diagnostics#4036
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Warning
- Copilot's review of this pull request may be incomplete because some of the changed files are excluded by your Copilot content exclusion settings. See Excluding content from Copilot for details.
Pull request overview
Removes obsolete setup diagnostics while preserving operational behavior and download-duration reporting.
Changes:
- Removes Zstandard, bundle-download, and Git-version diagnostics.
- Simplifies telemetry payload plumbing.
- Adds focused bundle-selection and download tests; removes the redundant Zstandard check.
Show a summary per file
| File | Description |
|---|---|
src/tools-download.ts |
Retains only download-duration status data. |
src/tools-download.test.ts |
Tests streamed and non-streamed reporting. |
src/setup-codeql.ts |
Removes Zstandard telemetry plumbing. |
src/setup-codeql.test.ts |
Expands cross-platform bundle-selection coverage. |
src/init.ts |
Removes Zstandard availability propagation. |
src/init-action.ts |
Stops emitting obsolete setup diagnostics. |
src/config-utils.ts |
Removes Git-version telemetry. |
src/codeql.ts |
Simplifies setup result propagation. |
src/codeql.test.ts |
Updates download-status assertions. |
pr-checks/checks/bundle-zstd.yml |
Removes the redundant Zstandard PR check. |
.github/workflows/__bundle-zstd.yml |
Generated, content-excluded workflow; not reviewed. |
lib/entry-points.js |
Generated, content-excluded JavaScript; not reviewed. |
Review details
Files excluded by content exclusion policy (2)
- .github/workflows/__bundle-zstd.yml
- lib/entry-points.js
- Files reviewed: 10/12 changed files
- Comments generated: 0
- Review effort level: Medium
mbg
left a comment
There was a problem hiding this comment.
Thanks! Removing these diagnostics makes sense and I am happy to approve this as-is.
I am wondering if it would still make sense for us to include some of this in our regular status reports? I have commented on the git version bit specifically, since that might be useful to understand long-term usage there.
| async function logGitVersionTelemetry( | ||
| config: Config, | ||
| gitVersion: GitVersionInfo, | ||
| ): Promise<void> { | ||
| if (config.languages.length > 0) { | ||
| addNoLanguageDiagnostic( | ||
| config, | ||
| makeTelemetryDiagnostic( | ||
| "codeql-action/git-version-telemetry", | ||
| "Git version telemetry", | ||
| { | ||
| fullVersion: gitVersion.fullVersion, | ||
| truncatedVersion: gitVersion.truncatedVersion, | ||
| }, | ||
| ), | ||
| ); | ||
| } | ||
| } |
There was a problem hiding this comment.
Rather than removing this entirely, would it make sense to include this in ordinary status reports?
There was a problem hiding this comment.
I don't think we have a need for it today, and it's easy to re-add. So I suggest we only add it when needed. Most repos scan frequently enough that we'll get good data after only a week.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Warning
- Copilot's review of this pull request may be incomplete because some of the changed files are excluded by your Copilot content exclusion settings. See Excluding content from Copilot for details.
Review details
Files excluded by content exclusion policy (2)
- .github/workflows/__bundle-zstd.yml
- lib/entry-points.js
- Files reviewed: 11/13 changed files
- Comments generated: 1
- Review effort level: Medium
Several CodeQL setup diagnostics were introduced to monitor rollouts that are now established, but they continue to add substantial SARIF and telemetry volume on every workflow run. Remove these obsolete diagnostics while preserving the setup behavior and the remaining download-duration status field.
This removes the Zstandard availability, bundle download, and Git version diagnostics and their unused payload plumbing. Operational Zstandard detection, bundle selection, streaming extraction, fallback behavior, Git discovery, and overlay compatibility checks remain unchanged. The redundant dedicated Zstandard PR check is removed; linked bundle selection is covered directly across Linux, macOS, Windows, and gzip fallback, while the existing toolcache check continues to exercise downloading and extraction.
Risk assessment
For internal use only. Please select the risk level of this change:
Which use cases does this change impact?
Workflow types:
dynamicworkflows (Default Setup, Code Quality, ...).Products:
analysis-kinds: code-scanning.analysis-kinds: code-quality.Environments:
github.comand/or GitHub Enterprise Cloud with Data Residency.How did/will you validate this change?
If something goes wrong after this change is released, what are the mitigation and rollback strategies?
How will you know if something goes wrong after this change is released?
Are there any special considerations for merging or releasing this change?
Merge / deployment checklist