| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
There was a problem hiding this comment.
Adds C/C++ support gates for overlay analysis by introducing dedicated feature flags and a per-language minimum CodeQL CLI version, aligning overlay enablement with language-specific rollout control.
Changes:
Copilot reviewed 14 out of 14 changed files in this pull request and generated 2 comments.
Show a summary per file| File | Description |
|---|---|
| src/overlay/index.ts | Adds the per-language minimum CLI version constant for C/C++ overlay analysis. |
| src/feature-flags.ts | Adds new C/C++ overlay feature flags and wires them into the feature flag configuration (env vars + minimum version). |
| lib/upload-sarif-action.js | Generated output reflecting the TypeScript changes. |
| lib/upload-sarif-action-post.js | Generated output reflecting the TypeScript changes. |
| lib/upload-lib.js | Generated output reflecting the TypeScript changes. |
| lib/start-proxy-action.js | Generated output reflecting the TypeScript changes. |
| lib/start-proxy-action-post.js | Generated output reflecting the TypeScript changes. |
| lib/setup-codeql-action.js | Generated output reflecting the TypeScript changes. |
| lib/resolve-environment-action.js | Generated output reflecting the TypeScript changes. |
| lib/init-action.js | Generated output reflecting the TypeScript changes. |
| lib/init-action-post.js | Generated output reflecting the TypeScript changes. |
| lib/autobuild-action.js | Generated output reflecting the TypeScript changes. |
| lib/analyze-action.js | Generated output reflecting the TypeScript changes. |
| lib/analyze-action-post.js | Generated output reflecting the TypeScript changes. |
You can also share your feedback on Copilot code review. Take the survey.
Sorry, something went wrong.
| [Feature.OverlayAnalysisCpp]: { | ||
| defaultValue: false, | ||
| envVar: "CODEQL_ACTION_OVERLAY_ANALYSIS_CPP", | ||
| minimumVersion: CODEQL_OVERLAY_MINIMUM_VERSION_CPP, | ||
| }, |
There was a problem hiding this comment.
I don't think this is necessary.
Sorry, something went wrong.
There was a problem hiding this comment.
This looks good — two things before we merge:
Sorry, something went wrong.
Wire C/C++ overlay feature flags into overlay mapping
|
Thanks @henrymercer! I addressed the comments here 0d057cc and 074a0db |
Sorry, something went wrong.
Co-authored-by: Henry Mercer <henrymercer@github.com>
| Back | FazBrowse Home | New Git URL |
I'm not sure if this has to be filled in for this specific case. If the reviewer thinks it's useful/mandatory I'll be happy to do it.
Risk assessment
For internal use only. Please select the risk level of this change:
Which use cases does this change impact?
Workflow types:
Products:
Environments:
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