Is there an existing issue for this?

• I have searched the existing issues

Does this issue exist in the latest version?

• I'm using the latest release

Describe the bug?

Lately, we upgraded to the latest version of changed files, and we are again facing problems with the script detecting too many files changed.

The expected outcome for this PR:
raycast/extensions#3245

Will be to get the files listed in the files changed section, but instead, we get many extra files that have been changed on the main repository between the time this PR was created till the Check is running.

On this run you can see all those files being listed. They are coming from all commits that have been done on the main repository and probably coming from "merge" action during checkout.

To Reproduce

1. Setup main repository
2. Fork the main repository
3. Push some commits to main repository
4. Push some commits to forked respository
5. Run a files-changed on PR created from the forked repository and observe multiple files being reported on top of PR changes.

What OS are you seeing the problem on?

all

Expected behavior?

I would expect to only see files that are listed in PR.
Instead of comparing to the BASE_SHA, it should instead compare to the commit that was used to do the merge, in our case 4ef2e916978e1c645499e3a6c7a536bdc3153403.

The last version that was behaving properly was v14.6 and it was really solid in this case. It was using a git log --no-merge to get proper SHA to compare to.

Relevant log output

No response

Anything else?

Is there a way to achieve the same behavior as in v14.6 for PRs?
We need to upgrade script version due to GitHub deprecations.

Code of Conduct

• I agree to follow this project's Code of Conduct