-
-
Notifications
You must be signed in to change notification settings - Fork 492
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
Pattern does not match any files #280
Comments
We get the same output as we are running this on our own self-hosted runner on our windows server 2019 machine. Could it have something to do with the latest dep update of actions/glob? |
For now our workaround is: uses: softprops/action-gh-release@v0.1.13 |
Thanks for the report. In the most recent update, the glob dep was upgraded from 7.1.6 to 8. https://github.com/isaacs/node-glob/blob/main/changelog.md#80 I see some changes which look like they affect windows users regarding the \ the character |
The latest glob readme recommends using forward slashes on windows https://github.com/isaacs/node-glob#windows I think I might be able to make this backwards compatible by detecting windows trying as is and then falling back by trying to replace \ with / |
latest action-gh-release broken with mixed win path: D:\a\OpenHantek6022\OpenHantek6022/build/packages/* not include valid file. Signed-off-by: Martin <Ho-Ro@users.noreply.github.com>
I see. OK, I migrated to forward slashes, which I like more than backward ones anyway. Thanks. |
Me too, but sometimes we're confronted with the nasty windows behaviour of backslashed pathes :( ...
uses: softprops/action-gh-release@v1
with:
prerelease: true
files: ${{github.workspace}}/build/packages/*
... This gives:
Any chance to "rectify" the As a quick fix I reverted to |
Until this is fixed: softprops/action-gh-release#280 Signed-off-by: Patrick Avery <patrick.avery@kitware.com>
Set release step version back to v0.1.13 because of bug, see: softprops/action-gh-release#280
Any progress? |
I switched to forward slashes, honestly why care? |
Because sometimes e.g. |
You can replace https://github.com/martinrotter/rssguard/blob/master/.github/workflows/rssguard.yml#L91 |
softprops/action-gh-release#280 Signed-off-by: Martin <Ho-Ro@users.noreply.github.com>
softprops/action-gh-release#280 Signed-off-by: Martin <Ho-Ro@users.noreply.github.com>
Thx, stupid me, I couldn't see the forest for the trees :) |
Any progress? |
softprops/action-gh-release globing doesn't support backslashes as directory separators and instead always treats them as the an escape character when a glob-based input under 'files' is detected. Because of this, have the release job run on ubuntu so that the zip artifact directory path environment variable declared at the workflow level will resolve to a path with forward slashes, since environment variables are only evaluated at the job level. See: softprops/action-gh-release#280
softprops/action-gh-release globing doesn't support backslashes as directory separators and instead always treats them as the an escape character when a glob-based input under 'files' is detected. Because of this, have the release job run on ubuntu so that the zip artifact directory path environment variable declared at the workflow level will resolve to a path with forward slashes, since environment variables are only evaluated at the job level. See: softprops/action-gh-release#280
softprops/action-gh-release globing doesn't support backslashes as directory separators and instead always treats them as the an escape character when a glob-based input under 'files' is detected. Because of this, have the release job run on ubuntu so that the zip artifact directory path environment variable declared at the workflow level will resolve to a path with forward slashes, since environment variables are only evaluated at the job level. See: softprops/action-gh-release#280
softprops/action-gh-release globing doesn't support backslashes as directory separators and instead always treats them as the an escape character when a glob-based input under 'files' is detected. Because of this, have the release job run on ubuntu so that the zip artifact directory path environment variable declared at the workflow level will resolve to a path with forward slashes, since environment variables are only evaluated at the job level. See: softprops/action-gh-release#280
softprops/action-gh-release globing doesn't support backslashes as directory separators and instead always treats them as the an escape character when a glob-based input under 'files' is detected. Because of this, have the release job run on ubuntu so that the zip artifact directory path environment variable declared at the workflow level will resolve to a path with forward slashes, since environment variables are only evaluated at the job level. See: softprops/action-gh-release#280
softprops/action-gh-release globing doesn't support backslashes as directory separators and instead always treats them as the an escape character when a glob-based input under 'files' is detected. Because of this, have the release job run on ubuntu so that the zip artifact directory path environment variable declared at the workflow level will resolve to a path with forward slashes, since environment variables are only evaluated at the job level. See: softprops/action-gh-release#280
softprops/action-gh-release globing doesn't support backslashes as directory separators and instead always treats them as the an escape character when a glob-based input under 'files' is detected. Because of this, have the release job run on ubuntu so that the zip artifact directory path environment variable declared at the workflow level will resolve to a path with forward slashes, since environment variables are only evaluated at the job level. See: softprops/action-gh-release#280
softprops/action-gh-release globing doesn't support backslashes as directory separators and instead always treats them as the an escape character when a glob-based input under 'files' is detected. Because of this, have the release job run on ubuntu so that the zip artifact directory path environment variable declared at the workflow level will resolve to a path with forward slashes, since environment variables are only evaluated at the job level. See: softprops/action-gh-release#280
can update after softprops/action-gh-release#280 is fixed
softprops#280 Document change in glob 8.0
* Add note about windows paths #280 Document change in glob 8.0 * Fix incorrectly escaped markdown backslashes
just use forward slashes see softprops/action-gh-release#280
Any update? |
Here is output of "dir":
But my script does not produce expected result:
Pattern should clearly match and it did match some weeks/month ago without any related changes in my code. Maybe some regression in your great code. :)
The text was updated successfully, but these errors were encountered: