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
[BUG] Looking for __init__.py is failing #582
Comments
@giladlevy7 Does the file exists in the repo ? |
@jackton1 yes, it exist (but it should work even if it doesn't, right?) |
Thanks for reporting this issue, don't forget to star this project if you haven't already to help us reach a wider audience. |
@giladlevy7 Can you also include your configuration of the https://github.com/actions/checkout? |
@jackton1 of course, thanks for helping.
|
@giladlevy7 Can you upgrade actions/checkout@v2 to v3 |
@giladlevy7 Closing this issue, for now, since a new version has been released. Let me know if the issue persists and I can reopen the issue. I also recommend that you enable debugging and post the entire log output i.e including the checkout and the changed files actions steps |
@jackton1
and unfortunately it still fails:
is it working for you with finding init.py file? i don't think it's the code checkout since if I'm looking for another file - it works, or without any filter - also works |
hi @jackton1 ! can we reopen that? |
@giladlevy7 See the link PR |
Thanks for reporting this issue, don't forget to star this project if you haven't already to help us reach a wider audience. |
@jackton1 thanks! |
Is there an existing issue for this?
Does this issue exist in the latest version?
Describe the bug?
I'm trying to use this GH workflow to verify whether a specific init.py file was modified or not.
I've tried to use regex, specific paths, and other options as well but it keeps failing with the following error:
Step content:
- name: Get changed files id: changed-files uses: tj-actions/changed-files@v34.6.1 with: files: | commons/__init__.py
To Reproduce
Add the following step:
What OS are you seeing the problem on?
ubuntu-latest or ubuntu-20.04
Expected behavior?
To succeed
Relevant log output
Anything else?
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: