| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
This PR prevents Copilot Code Review (CCR) runs from calling the feature flags API (which currently 403s with CCR credentials), and instead always uses default feature flag values to avoid confusing logs and unnecessary API traffic.
Changes:
Copilot reviewed 9 out of 9 changed files in this pull request and generated 1 comment.
Show a summary per file| File | Description |
|---|---|
| src/feature-flags.ts | Adds CCR detection to bypass remote feature-flag fetching and updates debug messaging for non-dotcom. |
| src/feature-flags.test.ts | Adds a CCR test case and refactors assertions to validate default-value behavior and expected logs. |
| lib/upload-sarif-action.js | Generated build output reflecting the feature flag behavior changes. |
| lib/start-proxy-action.js | Generated build output reflecting the CCR detection and feature flag behavior changes. |
| lib/setup-codeql-action.js | Generated build output reflecting the CCR detection and feature flag behavior changes. |
| lib/init-action.js | Generated build output reflecting the feature flag behavior changes. |
| lib/init-action-post.js | Generated build output reflecting the feature flag behavior changes. |
| lib/autobuild-action.js | Generated build output reflecting the CCR detection and feature flag behavior changes. |
| lib/analyze-action.js | Generated build output reflecting the feature flag behavior changes. |
Sorry, something went wrong.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
| Back | FazBrowse Home | New Git URL |
CCR's auth token does not currently have enough permissions to access the features API, so it 403s. This PR skips the API request and uses the default values for all feature flags. This is less confusing in the logs, saves a bit of time, and reduces a bit of API load.
The drawback is we'll need to back this change out once we get round to updating CCR and the features flag API to work together.
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