ci: experiment with changed files input for PR scope detection #6620
+35
−21
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
|
Thanks @JairoTM-es. Mind pushing an unrelated change in a different file, maybe? It doesn't seem to be working with the removed documentation link in the workflow, at least. |
|
✅ Generated APK variants! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description (required)
Related to #6588 (follow-up experiment)
What changes did you make and why?
This pull request is an experimental follow-up to evaluate the limitations identified in the previous PR scope check workflow.
Previously, the workflow only analyzed the PR title and description, which makes it unable to detect unrelated changes if they are not explicitly mentioned in the text.
In this PR, I added a step to collect the list of changed files between the PR branch and the base branch and pass that information as additional context to the analysis.
The goal is to test whether providing file-level context improves the detection of mixed or unrelated changes, without changing the original logic or prompt structure.
This PR is intentionally scoped for experimentation and validation only.
Tests performed (required)
(No Android build or emulator testing required, as this change only affects CI workflows.)
Screenshots (for UI changes only)
Not applicable.
Note: I have read CONTRIBUTING.md and kept this PR intentionally small and focused.