You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @jackton1 , I tried what you mentioned in #479, but it still turns out not working.
I tried with both v19 and v20 but always get "Non Matching modified files".
To Reproduce
with this Workflow:
jobs:
mark-header-automate:
runs-on: ubuntu-lateststeps:
- name: Check out a copy of the repouses: actions/checkout@v3with:
fetch-depth: 2path: main
- name: Get changed filesid: changed-filesuses: tj-actions/changed-files@v20with:
since_last_remote_commit: "true"path: mainfiles: | *.md **/*.md **/**/*.md **/**/**/*.md **/**/**/**/*.md **/**/**/**/**/*.md **/**/**/**/**/**/*.md **/**/**/**/**/**/**/*.md **/**/**/**/**/**/**/**/*.md **/**/**/**/**/**/**/**/**/*.md **/**/**/**/**/**/**/**/**/**/*.mdfiles_ignore: | *.yml **/*.yml *.png **/*.png
Also since_last_remote_commit: true when using fetch-depth: 2 works because the action correctly detects this misconfiguration i.e you're saying compare the last remote commit but the checkout action fetches only 2 commits which in some cases doesn't have the previous remote commit.
Is there an existing issue for this?
Does this issue exist in the latest version?
Describe the bug?
Hi @jackton1 , I tried what you mentioned in #479, but it still turns out not working.
I tried with both v19 and v20 but always get "Non Matching modified files".
To Reproduce
What OS are you seeing the problem on?
ubuntu-latest or ubuntu-20.04
Expected behavior?
@jack-fireworkhq That’s because the pattern itself is invalid.
You’ll need to remove the single quotes you have around the pattern.
Should be modified to
OR
Originally posted by @jackton1 in #479 (comment)
I expect what you mentioned above should be able to work.
Relevant log output
Anything else?
I tried a lot🤣, but none of them worked. Let me know if you need anything more to work on this, thanks.
Code of Conduct
The text was updated successfully, but these errors were encountered: