Skip to content
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

[bug] Creates a subdirectory named "artifact" under the specified path location #356

Open
lnxpy opened this issue Oct 2, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@lnxpy
Copy link

lnxpy commented Oct 2, 2024

What happened?

This is my upload artifact step:

      - name: Upload badges as artifact
        uses: actions/upload-artifact@v3
        with:
          path: .pypi_chart/${{ matrix.package }}_badge.svg

and this is my download artifact step:

      - name: Download badges artifact
        uses: actions/download-artifact@v3
        with:
          path: .pypi_chart/
          merge-multiple: true

I expect all my .svg files to be stored under the .pypi_chart/ directory like:

  • .pypi_chart/1.svg
  • .pypi_chart/2.svg
  • .pypi_chart/3.svg

But it creates a subdirectory called .pypi_chart/artifact/ and places those svg files there.

What did you expect to happen?

How can we reproduce it?

Anything else we need to know?

What version of the action are you using?

v3

What are your runner environments?

linux

Are you on GitHub Enterprise Server? If so, what version?

No response

@lnxpy lnxpy added the bug Something isn't working label Oct 2, 2024
@mbriziarelli
Copy link

mbriziarelli commented Dec 5, 2024

Yes @lnxpy
This is a severe bug that I experienced myself. I spent hours trying to debug before understanding that the problem was not in my code.
What's happening : when you don't specify artifact name, actions/download-artifact@v4 creates the artifact folder as you describe.

The only way to not experience this bug that I have discovered is to give a name to the artifact when uploading and downloading.

@lnxpy
Copy link
Author

lnxpy commented Dec 5, 2024

@mbriziarelli Nice. Exactly. I was struggling with it until you showed up. Wish they fix it. Another solution might be to download the artifacts in ../ and specify a directory name for the artifacts. Not sure if it works though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants
@mbriziarelli @lnxpy and others