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
Describe the bug
If path to a file involves a symbolic link, the file is not found
Version
V1
V2
Environment
self-hosted
Linux
Windows
Mac
How to reproduce
Running as
- name: Archive production artifactsuses: actions/upload-artifact@v2with:
name: Store executablepath: .build
Works, and the big zip file looks as follows:
When trying this, though:
- name: Archive production artifactsuses: actions/upload-artifact@v2with:
name: Store executablepath: .build/release/prism.exe
It fail, since release is actually a symlink to to x86_64-unknown-windows-msvc/release.
Using .build/x86_64-unknown-windows-msvc/release/prism.exe directly does work.
Notice also that the downloaded ZIP contains a double copy of this since the symlink is resolved as a regular uploaded file and not counted as a symbolic link (This seems to be related to #93)
The text was updated successfully, but these errors were encountered:
Describe the bug
If
path
to a file involves a symbolic link, the file is not foundVersion
Environment
How to reproduce
Running as
Works, and the big zip file looks as follows:
When trying this, though:
It fail, since
release
is actually a symlink to tox86_64-unknown-windows-msvc/release
.Using
.build/x86_64-unknown-windows-msvc/release/prism.exe
directly does work.Notice also that the downloaded ZIP contains a double copy of this since the symlink is resolved as a regular uploaded file and not counted as a symbolic link (This seems to be related to #93)
The text was updated successfully, but these errors were encountered: