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
Up to v35 it was possible to specify directories to check for changed files without adding a glob pattern at the end. Now this seems to be required, but I am not sure if this is desired behaviour or accidental bug since README says it should be possible without glob pattern:
files: docs/*.{js,html} # Alternatively using: `docs/**` or `docs`
Make any changes in a workflow file. Second step gets skipped. Adding the glob pattern at the end (.github/workflows/**) makes it work again. Alternatively, change version to v35 and it also works again.
What OS are you seeing the problem on?
ubuntu-latest or ubuntu-20.04
Expected behavior?
The changed files in a directory should be recognized again without explicitly adding the glob pattern at the end. Alternatively, the README could be clearer to bring out that this is required now.
Is there an existing issue for this?
Does this issue exist in the latest version?
Describe the bug?
Up to v35 it was possible to specify directories to check for changed files without adding a glob pattern at the end. Now this seems to be required, but I am not sure if this is desired behaviour or accidental bug since README says it should be possible without glob pattern:
To Reproduce
Using the following steps:
Make any changes in a workflow file. Second step gets skipped. Adding the glob pattern at the end (
.github/workflows/**
) makes it work again. Alternatively, change version to v35 and it also works again.What OS are you seeing the problem on?
ubuntu-latest or ubuntu-20.04
Expected behavior?
The changed files in a directory should be recognized again without explicitly adding the glob pattern at the end. Alternatively, the README could be clearer to bring out that this is required now.
Relevant log output
Anything else?
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: