| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
There was a problem hiding this comment.
This PR adds support for the Repository Properties API to the CodeQL Action, enabling organization-wide query configuration through repository properties.
Key changes:
Copilot reviewed 22 out of 22 changed files in this pull request and generated 2 comments.
Show a summary per file| File | Description |
|---|---|
| src/feature-flags/properties.ts | New module for Repository Properties API integration and property name enumeration |
| src/init-action.ts | Adds repository properties loading during action initialization |
| src/config/db-config.ts | Implements query combination logic with repository property precedence |
| src/error-messages.ts | Adds error message functions for repository property validation |
| src/config-utils.ts | Updates Config interface and initialization to include repository properties |
| src/testing-utils.ts | Updates test utilities to include repository properties field |
| package.json | Simplifies test script pattern matching |
| lib/*.js | Generated JavaScript files reflecting the TypeScript changes |
| .github/actions/check-codescanning-config/index.ts | Adds query array sorting for deterministic config comparison |
Sorry, something went wrong.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Looks like some additional config normalisation is needed in the tests, otherwise LGTM.
Sorry, something went wrong.
Also add `logger.debug` call with keys from API response
There was a problem hiding this comment.
Looks reasonable, and the test run checks out.
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
This PR has two main contributions:
For the Repository Properties support, we fetch the list of repository properties at the start of the init Action. We filter this down to known properties (i.e. ones we care about) and store their values. The mapping of known property names to their values is then included in the Action state (i.e. the Config type) so that it remains accessible to other CodeQL Action steps in the same workflow and with consistent values.
For the query augmentation, we give the value obtained from the Repository Properties the highest precedence. This is because the intention here is to allow organisations to configure org-wide queries to include in analyses.
Risk assessment
For internal use only. Please select the risk level of this change:
Merge / deployment checklist