-
-
Notifications
You must be signed in to change notification settings - Fork 176
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] files_ignore
input ignores negation with !
#1681
Comments
Thanks for reporting this issue, don't forget to star this project if you haven't already to help us reach a wider audience. |
ignore_files
input ignores negation with !
files_ignore
input ignores negation with !
@luk-lo The If you intend to include ...
- name: Non-txt file changes except in module3
id: diff-non-txt
uses: tj-actions/changed-files@af292f1e845a0377b596972698a8598734eb2796 # v40.0.0
with:
files: |
**
module3/**/*.txt
files_ignore: '**/*.txt' |
@jackton1 Thanks for the change and the quick response. My issue is that if I set |
Hi @luk-lo, yes it’s possible I’ve updated my comment above to reflect the change you’ll need to make |
Hi @jackton1 thank you very much, that worked like a charm. for the record: yaml does not like multi-line-string lines starting with |
@jackton1 sorry I spoke too early. With the new configuration, changes to |
Hi @luk-lo, this should be resolved now. You can re-run the workflow if you use the major version or upgrade to the latest patch release. |
It works 👍 thanks again |
Hi @luk-lo a new release introduced a new input |
Is there an existing issue for this?
Does this issue exist in the latest version?
Describe the bug?
I have a scenario where I want to list all changes but ignore
.txt
files except if those files are belowmodule3
via thefiles_ignore
input:But if I modify e.g.
module3/test/file.txt
, it does not appear inall_changed_files
. The log output looks to me like the entries infiles_ignore
are prepended with!
except when they already have a!
in front?To Reproduce
I reproduced the behavior in luk-lo/test-issue#1
What OS are you seeing the problem on?
ubuntu-latest or ubuntu-22.04
Expected behavior?
I would expect the
.txt
files belowmodule3
to not be ignored.Relevant log output
Has all relevant logs been included?
Anything else?
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: