Repository navigation
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Potential bug: The
git diffscope was broadened, but the file filtering logic was not updated, causing all E2E tests to run unnecessarily for most infrastructure changes.Description: The
git diffcommand ingetChangedTestAppswas changed to scan for file changes across the entire repository (-- .) instead of being limited to thedev-packages/e2e-tests/directory. However, the subsequent logic still checks if every changed file starts with thedev-packages/e2e-tests/test-applications/prefix. If any file outside this specific subdirectory is changed (e.g., a change to the test infrastructure filegetTestMatrix.tsitself), the function returnsfalse. This causes the CI pipeline to run all E2E tests, defeating the purpose of the selective test matrix optimization and leading to significantly longer CI execution times.Suggested fix: Revert the path specifier in the
git diffcommand from-- .back to the more specific-- dev-packages/e2e-tests/. This ensures the command only considers file changes within the E2E tests package, which aligns with the existing filtering logic and restores the intended selective test execution.severity: 0.65, confidence: 0.98
Did we get this right? 👍 / 👎 to inform future reviews.