[BUG] `path` input does not work in combination with Github API approach about changed-files

[jackton1]

Hi @gstokkink, the path input is only required when you clone the repository and wouldn’t be useful otherwise.

See: https://github.com/tj-actions/changed-files/blob/main/src/inputs.ts#L250-L269 for a full list of unsupported inputs when using GitHub’s API

[gstokkink]

@jackton1 maybe it should raise an error then? Or is that too complicated 😄 Anyway, that just means I will have to prefix the file paths manually. Thanks for the reply.

[jackton1]

Hi @gstokkink not sure what you mean by I will have to prefix the file paths manually if you plan to change your working directory you can do so but none of that information is used to determine the list of changed files which only relies on the pull request number. Hopefully that provides some clarification.

[gstokkink]

@jackton1 I meant prefixing the file patterns with the path I'm interested in. In this case the monorepo contains three apps apps/A, apps/B and apps/C. In one job I'm then only interested in the file changes for, e.g., apps/A.

With the local .git directory approach I could then set the path input to apps/A and use file pattern **.rb, for example. The list of changed files would then also be relative to this directory. With the Github REST API approach I have to use the pattern apps/A/**/*.rb, and also manually chop off the apps/A prefix from the list of changed files when processing these as paths relative to the apps/A directory.