A green check on GitHub Actions tells you a workflow succeeded. To retrieve a file it produced, open the exact run and look for an artifact on the run summary.

Open the repository’s Actions tab and select the workflow.

Choose the run for the branch and commit you actually want. Avoid guessing from the timestamp alone.

Under Artifacts, download the named archive. You need to be signed in and have read access to the repository.

No artifact listed?

Open the upload step’s log. Check whether the step ran, whether the configured path matched any files, and whether the artifact is still within its retention period. If the output stayed on the runner and was never uploaded, the run summary cannot supply it later.

If you use the GitHub CLI, download a specific artifact with gh run download RUN_ID -n ARTIFACT_NAME. Explicit names such as ios-test-results are easier to recognize than generic names like output.

GitHub’s artifact download guide

Example: QA needs the test results from a pull request

Open the run linked to the pull request’s checks, verify the commit SHA, and look for an archive named for the job or test suite. If the workflow has several jobs or runs the same tests against multiple simulators, inspect the artifact name before downloading. An archive from a different job can look plausible while containing the wrong results.

Three ways an artifact goes missing

The upload was skipped: Expand the job log and look for the upload step. A failed test can prevent a later step from running under its default condition. If reports should survive test failures, configure the upload step accordingly and verify that the test actually wrote the report.

The path matched nothing: Compare the exact path produced by the build with the upload step’s input, including the working directory. Consider making missing files an explicit failure for outputs the team depends on.

The artifact expired: Check repository retention settings. If you need the output again, rerun the original workflow if it is still reproducible. Label the newly produced archive with its run details so reviewers know what they received.

Before sending a link, check that the recipient has repository read access and share the run URL with the exact artifact name. That gives them enough information to find the right archive.