Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Seems like this repo is ABANDONED, alternatives suggestion #65

Open
Stas-AbsoluteDesign opened this issue Feb 23, 2023 · 5 comments
Open

Comments

@Stas-AbsoluteDesign
Copy link

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
Copy link

ravenium commented Feb 24, 2023

@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
Copy link
Author

@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
Copy link

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

see #55

@ravenium
Copy link

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

@matveym
Copy link

matveym commented May 4, 2023

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"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants