Prepare for rolling out skipping computing file coverage information on PRs

[henrymercer]

Prepare for rolling out skipping computing file coverage information on PRs to speed up analysis.

• Gate the feature behind a CLI feature that updates the logs to account for file coverage information no longer being expected.
• Add a repository property that can be used to continue computing file coverage information on PRs.
• Add a telemetry diagnostic so we can see whether this is being used.
• Remove the restriction to the github org.

Note that the CLI tools feature flag is not yet released, even as a nightly. Though given it that CLI feature only modifies logs, I don't think we need to wait for a release before merging this PR.

Risk assessment

For internal use only. Please select the risk level of this change:

• Low risk: Changes are fully under feature flags, or have been fully tested and validated in pre-production environments and are highly observable, or are documentation or test only.

Which use cases does this change impact?

Workflow types:

• Advanced setup - Impacts users who have custom CodeQL workflows.
• Managed - Impacts users with dynamic workflows (Default Setup, Code Quality, ...).

Products:

• Code Scanning - The changes impact analyses when analysis-kinds: code-scanning.

Environments:

• Dotcom - Impacts CodeQL workflows on github.com and/or GitHub Enterprise Cloud with Data Residency.

How did/will you validate this change?

• Unit tests - I am depending on unit test coverage (i.e. tests in .test.ts files).

If something goes wrong after this change is released, what are the mitigation and rollback strategies?

• Feature flags - All new or changed code paths can be fully disabled with corresponding feature flags.

How will you know if something goes wrong after this change is released?

• Telemetry - I rely on existing telemetry or have made changes to the telemetry.
  • Alerts - New or existing monitors will trip if something goes wrong with this change.

Are there any special considerations for merging or releasing this change?

• No special considerations - This change can be merged at any time.

Merge / deployment checklist

• Confirm this change is backwards compatible with existing workflows.
• Consider adding a changelog entry for this change.
• Confirm the readme and docs have been updated if necessary.

[Copilot]

Pull request overview

Prepares a controlled rollout to skip computing file coverage information on PR analyses (to improve performance) by gating the behavior on a CodeQL CLI tools feature, adding a repository property opt-out, and emitting telemetry to observe usage.

Changes:

• Add a new CodeQL CLI tools feature (suppressesMissingFileBaselineWarning) and gate SkipFileCoverageOnPrs behind it.
• Allow org-owned repositories to opt back into file coverage on PRs via the github-codeql-file-coverage-on-prs repository property.
• Add telemetry for when the repository property is used, plus update unit tests and changelog.

Reviewed changes

Copilot reviewed 19 out of 19 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
src/tools-features.ts	Adds a new CLI tools feature enum value used to gate the rollout.
src/feature-flags.ts	Gates SkipFileCoverageOnPrs behind the new CLI tools feature.
src/feature-flags/properties.ts	Adds and parses the new repository property github-codeql-file-coverage-on-prs.
src/init.ts	Updates file-coverage enablement logic to support repository-property opt-in and uses CLI-gated feature evaluation.
src/init-action.ts	Passes repository properties into config calculation and emits telemetry when repo property enables PR file coverage.
src/init.test.ts	Updates unit tests for the revised file-coverage enablement logic and new opt-in behavior.
CHANGELOG.md	Documents the experimental rollout and the repository-property opt-out mechanism.
lib/upload-sarif-action.js	Generated JS output updated to reflect TS changes.
lib/upload-sarif-action-post.js	Generated JS output updated to reflect TS changes.
lib/upload-lib.js	Generated JS output updated to reflect TS changes.
lib/start-proxy-action.js	Generated JS output updated to reflect TS changes.
lib/start-proxy-action-post.js	Generated JS output updated to reflect TS changes.
lib/setup-codeql-action.js	Generated JS output updated to reflect TS changes.
lib/resolve-environment-action.js	Generated JS output updated to reflect TS changes.
lib/init-action.js	Generated JS output updated to reflect TS changes.
lib/init-action-post.js	Generated JS output updated to reflect TS changes.
lib/autobuild-action.js	Generated JS output updated to reflect TS changes.
lib/analyze-action.js	Generated JS output updated to reflect TS changes.
lib/analyze-action-post.js	Generated JS output updated to reflect TS changes.

[mbg]

This LGTM as-is, but I have a couple of suggestions for tidying up the implementation. I also think we should add a page to docs.github.com for the available repository properties that are understood by the CodeQL Action.

[mbg]

We should add documentation on docs.github.com about these repo properties. I have created an internal issue to track this.

[mbg]

Minor: we have repositoryPropertiesResult.orElse({}) at least a couple of times here now. Consider adding const repositoryProperties = repositoryPropertiesResult.orElse({}); somewhere before the uses, or indeed modifying the code so that we never end up with the "result" here, but only the properties we loaded or {}.

[mbg]

This now duplicates most of getFileCoverageInformationEnabled. While we can't use getFileCoverageInformationEnabled as a shortcut here, consider whether you can move the code that emits this diagnostic into getFileCoverageInformationEnabled and end up with a cleaner solution in there?