Seems like this repo is ABANDONED, alternatives suggestion

[Stas-AbsoluteDesign]

So the last change has been made back to 2020! And new GitHub Actions release will deprecate some critical functionality.
So as a warning to anyone using this plugin - you should consider alternatives.

The original one I was able to find is:
https://github.com/marketplace/actions/changed-files
It has over 800+ stars and seems very popular and still has updates released quite often (3 days ago at the date this issue was created).
Any other alternatives are welcome.

[ravenium]

@Stas-AbsoluteDesign Any idea what specific functionality it's deprecating? I noticed a Node 12 vs 16 warning today (and some set-output warnings) but that was about it.

The only reason I went against tj-actions is that it has to checkout the entire repo to compare for changed files. This wouldn't be the end of the world (only lasts for the life of the workflow) except the tool I am using after it only works on directories and not individual files. I had to basically rm -rf before running the next action (which downloads only the changed files in the PR for processing in the tool action).

I'm sure there's a better way but I haven't stumbled across it yet. (using https://github.com/Bhacaz/checkout-files to grab the individual changed files)

[Stas-AbsoluteDesign]

@ravenium well, the breaking change is set:output GutHub deprecation, there will be a new way of outputting variables.
They aim to put it down later this year: "This will come into effect starting on September 27th". So by the look of no issues or updates made to this repository - it seems that at the date above it will be just completely dead\non-functional.

This issue's purpose is mainly to warn people to avoid using it in the long term run. And as it comes up very early when you search "git changes" on the marketplace and has lots of starts\installs - it is better to draw attention here. Probably, it is even worth adding an "abandoned" label straight to the readme file to show this message on marketplace\github to avoid the further spreading of an abandoned tool.

[subelsky]

Looks like @masesdevelopers came to the rescue with https://github.com/masesgroup/retrieve-changed-files

see #55

[ravenium]

I ended up manually writing git diff commands in a custom action. This definitely looks a bit more elegant :)

[matveym]

Yep, git diff is very easy to do:

           - name: Get changed files
              id: changed-files
              run: |
                  git fetch origin master
                  diff=$(git diff --name-only --diff-filter=AM origin/main..HEAD | tr '\n' ' ')
                  echo "ADDED_MODIFIED=$diff" >> "$GITHUB_OUTPUT"

[necipallef]

Here is my implementation that uses git diff, it doesn't rely on main branch and it outputs every changed file:

           - name: Git clone
              uses: actions/checkout@v4
           - name: Get changed files
              id: changed-files
              run: |
                  git fetch origin $GITHUB_BASE_REF
                  diff=$(git diff --name-only origin/$GITHUB_BASE_REF..HEAD)
                  echo $diff
                  for changed_file in $diff; do
                      echo $changed_file
                  done