dawnl.ink for GitHub

Insert the GitHub URL of a workflow file that uses actions/upload-artifact.

Note that the branch you are on also matters.

To allow any completed runs, not only successful ones, append ?status=completed to the URL.

If you have several workflows or branches, you can adapt the URL by hand in a predictable way.

If GitHub gave you a link such as the one below, change the github.com prefix to this site:

You get a download URL that works the same but does not show a 404 to visitors who are not logged into GitHub.

Or paste the GitHub link into the field above.

A run is basically a collection of jobs. Even though it is the job that produces artifacts, they are associated with the parent run.

Example run:

You must provide the run to dawnl.ink to find artifacts. Again, change the prefix like in the example above.

If you click into a job instead, you can access its logs. Example job:

Raw log downloads are in the same situation as artifacts: dawnl.ink is needed for anonymous users. It accepts the job URL and the link from the "View raw logs" menu item.

For projects developing an application, it is useful to quickly try out the executable built from an incoming pull request. You can do this by clicking into a finished GitHub Actions job, then its parent run, then scrolling to the artifacts list.

Instead, you can use a more convenient approach: add a bot that replies with links directly to the artifacts as soon as the pull request finishes building.

Apply it to your repository by copying the sample workflow file. It must be on the default branch and fully merged before it will do anything.

Another advantage is that users who are not logged into GitHub can download the artifacts. If you do not need that, adapt the sample workflow to link directly to github.com without this site.

This ability is not part of dawnl.ink itself, just a creative way to apply it; the bot runs entirely within GitHub Actions in your repository.