We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It seems the repo name changed from changed-files to changed. Now the for workflow to work it should be:
changed-files
changed
uses: tj-actions/changed@v23.1
All README occurrences should be changed. I can happily help with that if that is the only place to change the documentation. LMK.
Getting action download info Error: Unable to resolve actions. Repository not found: tj-actions/changed-files.
ubuntu-latest or ubuntu-20.04
Workflow should be executed as usual.
No response
The text was updated successfully, but these errors were encountered:
Thanks for reporting this issue, don't forget to star this project to help us reach a wider audience.
Sorry, something went wrong.
Heya, +1ing this as we have a bunch of workflows that use this action and the repository name change has broken them all 😢
@marcus-crane @po5i Sorry for the mix up I assumed GitHub would redirect request to the new name. Based on https://github.blog/2013-05-16-repository-redirects-are-here/ but it doesn’t appear to work for GitHub actions. The name change has been reverted.
Things should be back to normal. 🙏🏽
GitHub issue: github/docs#15575
No branches or pull requests
Is there an existing issue for this?
Does this issue exist in the latest version?
Describe the bug?
It seems the repo name changed from
changed-files
tochanged
. Now the for workflow to work it should be:All README occurrences should be changed. I can happily help with that if that is the only place to change the documentation. LMK.
To Reproduce
What OS are you seeing the problem on?
ubuntu-latest or ubuntu-20.04
Expected behavior?
Workflow should be executed as usual.
Relevant log output
No response
Anything else?
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: