| 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 moves the conversion of PR diff-range paths to absolute paths from getDiffRanges in diff-informed-analysis-utils.ts to writeDiffRangeDataExtensionPack in analyze.ts. This refactoring enables getDiffRanges to be used from the init action in future changes, as it will now return relative paths instead of absolute paths. The conversion to absolute paths now happens when writing the extension pack, which is where the absolute paths are actually required.
Copilot reviewed 12 out of 12 changed files in this pull request and generated no comments.
Show a summary per file| File | Description |
|---|---|
| src/diff-informed-analysis-utils.ts | Removes absolute path conversion from getDiffRanges, now returns relative paths |
| src/diff-informed-analysis-utils.test.ts | Updates test expectations to match relative paths returned by getDiffRanges |
| src/analyze.ts | Adds diffRangeExtensionPackContents function that converts relative paths to absolute when creating extension pack |
| src/analyze.test.ts | Adds unit test for diffRangeExtensionPackContents function |
| src/upload-lib.ts | Updates filterAlertsByDiffRange to compare relative paths, exports function for testing |
| src/upload-lib.test.ts | Adds unit test for filterAlertsByDiffRange function |
| src/testdata/pr-diff-range.yml | New test fixture for extension pack content |
| src/testdata/valid-sarif-diff-filtered.sarif | New test fixture for filtered SARIF output |
Sorry, something went wrong.
…nge-absolute-path-conversion * origin/main: (32 commits) Add changelog note Update default bundle to codeql-bundle-v2.24.3 Bump tar from 7.5.7 to 7.5.10 Rebuild Rebuild Bump actions/upload-artifact from 6 to 7 in /.github/workflows Bump actions/download-artifact from 7 to 8 in /.github/workflows Bump the npm-minor group with 2 updates Fix some tests that should be serial Update method naming and JSDoc Rename to `EnabledOverlayConfig` Address review comments Use `Result`s for enablement return types Add disabled by env var disablement reason Rename to `usesDefaultQueriesOnly` Update `NonDefaultQueries` documentation Refactor `getOverlayDatabaseMode` and add new disablement reason Address review comments Add JSDoc Sort `OverlayDisabledReason` enum ...
There was a problem hiding this comment.
LGTM once we solve the merge conflict.
Sorry, something went wrong.
…rsion * main: (112 commits) Rebuild Update changelog and version after v4.33.0 Add changelog entry for #3570 Bump minor version Update changelog for v4.32.7 Only emit one message with accumulated property names Remove `cache-dependency-path` options as well Remove `package-lock.json` that's no longer needed Add step (in root directory) to install dependencies Add explicit cache dependency paths in `pr-checks.yml` Fix linter errors in `sync-back.test.ts` Fix linter errors in `sync-back.ts` Rename `sync_back` to `sync-back` Fix linter errors in `sync.ts` Add eslint configuration for `pr-checks` Add minimal `Step` type Add `workspaces` to root `package.json` Avoid bundling `package.json` Move `ava` config out of `package.json` Emit warning for unrecognised repo properties with our common prefix ... # Conflicts: # lib/init-action-post.js
| Back | FazBrowse Home | New Git URL |
Diff-informed analysis expects paths in the diff-range extension pack to be absolute paths. The conversion to absolute paths currently happens within getDiffRanges in diff-informed-analysis-utils.ts. This PR moves the conversion to writeDiffRangeDataExtensionPack in analyze.ts instead to allow getDiffRanges to be used from the init action in a future PR. As a result the diff-range paths written to pr-diff-range.json will be relative instead of absolute after this PR. This also requires a change to filterAlertsByDiffRange in upload-lib to filter based on relative paths instead of absolute paths.
The actual change occurs in commit 4. Commits 1 and 3 adds unit tests for affected functions and commit 2 exposes a function for testing.
Diff-informed analysis is guarded by the diff_informed_queries feature flag. The diff_informed_queries flag is already fully rolled out.
Risk assessment
For internal use only. Please select the risk level of this change:
Which use cases does this change impact?
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?
Merge / deployment checklist