-
-
Notifications
You must be signed in to change notification settings - Fork 444
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
files option does not respect working-directory setting #458
Comments
Can you share a link to your workflow? There's nothing in particular we do to manage your working directories. I believe the configuration option you mentioned simply switches the working directory before running the action rather than providing the job steps' |
here is an excerpt, hope this helps:
where If this workflow looks good to you, I can try to provide a minimal reproducible repo. |
I think I see the issue the following settings the working directory for each step. think of it like the PWD path when executing a step defaults:
run:
working-directory: ./frontend In your files declaration you provide the pattern - name: Deploy to GitHub release
uses: softprops/action-gh-release@v2
with:
files: frontend/dist/*.zip Could you try and remove the frontend prefix from that step? Since the working-directory is frontend that would then resolve to something like - name: Deploy to GitHub release
uses: softprops/action-gh-release@v2
with:
files: dist/*.zip |
afaik,
is working (current working version of my workflow), but
does not work (cannot find anything matching |
What happens when you remove the frontend part of the path after setting the working directory to frontend? |
I am having the very same issue. In my case is pretty much the same but is a rust application. |
files
option does not seem to respectjobs.<job_name>.defaults.run.working-directory
from github. I have to prepend working directory path to every file underfiles
for gh actions to find the correct file.The text was updated successfully, but these errors were encountered: