Sharing build outputs across different repositories is a common requirement for complex CI/CD pipelines, such as when an API gateway needs a binary built by a separate authentication service. While GitHub Actions natively supports passing artifacts between jobs in the same workflow, downloading them from a completely different repository requires explicit configuration and elevated permissions. Prerequisites for Cross-Repository Downloads
By default, the GITHUB_TOKEN provided to a workflow is scoped only to its own repository. To reach into another repository, you must use a or a GitHub App token . github actions download artifact from another repository
steps: - name: Download latest successful artifact uses: dawidd6/action-download-artifact@v6 with: github_token: ${{ secrets.ORG_ARTIFACT_TOKEN }} repo: owner/source-repo workflow: build.yml # Filename of the source workflow name: production-assets workflow_conclusion: success # Only get artifacts from passing runs branch: main # Target a specific branch Use code with caution. Comparison of Methods Store and share data with workflow artifacts - GitHub Docs Sharing build outputs across different repositories is a