- name: Download Build Artifact uses: actions/download-artifact@v4 with: name: my-artifact-name path: ./destination-folder # Optional: defaults to $GITHUB_WORKSPACE Use code with caution. 2. Downloading All Artifacts
By default, the action downloads an artifact by its name into the current workspace. artifact download github actions
- name: Download from another run uses: actions/download-artifact@v4 with: name: specific-artifact run-id: 123456789 # The ID of the run containing the artifact github-token: ${{ secrets.MY_PAT }} Use code with caution. Key Features and Recent Updates Whether you need to pass a compiled binary
: The v4 update introduced a backend architecture that can make downloads up to 90% faster than previous versions. Advanced Usage with GitHub CLI Store and share data with workflow artifacts - GitHub Docs artifact download github actions
Downloading artifacts in is a fundamental process for sharing data between different jobs in a workflow. Whether you need to pass a compiled binary to a testing suite or move build files to a deployment job, the actions/download-artifact action is the primary tool for this task. How to Download Artifacts in Your Workflow
If you omit the name parameter, GitHub will download every artifact associated with the current workflow run. Each artifact will be placed in a subdirectory named after the artifact itself unless the merge-multiple: true flag is used. 3. Cross-Workflow & Cross-Repo Downloads
: Versions v4 and newer automatically compute and verify SHA-256 digests to ensure that the downloaded artifact is identical to the one uploaded.