This service lets you get a shareable link to download a build artifact from the latest successful GitHub Actions build of a repository.
Any public repository is accessible by default and visitors don't need to log in.
If you'll be publishing a link to your own repository's artifacts, please install the GitHub App anyway, so that downloads for your repositories don't share the global API rate limit. The throttling will likely become very bad over time.
Check out the following sections to see what you can do with this.
Insert the GitHub URL of a workflow file that uses actions/upload-artifact.
Note that the branch which you're on also matters.
Following this form (and having selected the "Windows" artifact), you will end up at
which is a link that always downloads the latest artifact from a succeeding run on that repo+workflow+branch.
To allow any completed workflow 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 https://github.com/quassel/quassel/suites/2377181345/artifacts/50455732,
you can just change the prefix to https://nightly.link/quassel/quassel/suites/2377181345/artifacts/50455732,
and you get a download URL that works the same but doesn't give a "404" error to users who aren't logged into GitHub.
Or, paste it into the field above.
A run is basically a collection of jobs. Even though it's the job that produces artifacts, they get associated with the parent run.
Example run: https://github.com/quassel/quassel/actions/runs/701055013.
You have to provide the run to nightly.link if you want to find the artifacts.
Again, you can just change the prefix like https://nightly.link/quassel/quassel/actions/runs/701055013 to get there.
If, instead, you click into a job, you can access its logs.
Example job: https://github.com/oprypin/nightly.link/runs/1849327325?check_suite_focus=true
The raw log download link is in the same situation as artifacts: nightly.link is needed to make them work for anonymous users. It accepts both the job's URL itself, and the link that you can get from the "View raw logs" item.
For projects developing an application, it is useful to quickly try out the executable built from the code of an incoming pull request. You can do this normally by clicking into a finished GitHub Actions job, then into its parent run, then scrolling down to the list of artifacts.
Instead, you can opt into a much more convenient approach: add a "bot" that replies with links directly to the artifacts, as soon as the pull request finishes building.
Here's how it looks. Apply it to your repository by copying the sample workflow file.
Another advantage that this gives is that users that aren't logged into GitHub can download the artifacts as well. If you don't care about that, you can adapt the sample workflow to link directly to github.com, without relying on this site.
Note that this ability is not actually part of nightly.link, just a creative way to apply it; the "bot" is executed entirely within GitHub Actions, isolated to your repository.
GitHub has no direct way to directly link to the latest build from GitHub actions of a given repository.
Even if you do have a link to an artifact, using it requires the visitor to be logged into the GitHub website.
The discussion originates at actions/upload-artifact "Artifact download URL only work for registered users".
So, this service is a solution to this omission.
Because GitHub doesn't provide any permanent and public links to an artifact, this service redirects to time-limited links that GitHub can give to the application -- only on behalf of an authenticated user that has access to the repository. So, whenever someone downloads an artifact from a repository that you had added, this service uses a token that is associated with your installation of the GitHub App.
This GitHub App requests these permissions:
- Actions: Workflows, workflow runs and artifacts.
- Access: Read-only
- Metadata [mandatory]: Search repositories, list collaborators, and access repository metadata.
- Access: Read-only
Interestingly, the prompt that GitHub presents to you when authenticating to the service says something quite a bit scarier:
nightly.link by Oleh Prypin would like permission to:
- Verify your GitHub identity ($username)
- Know which resources you can access
- Act on your behalf
In reality, this blurb is completely generic and will be shown for any GitHub App authorization regardless of its permissions. This is discussed here.
Furthermore, the permissions that the app asks for are granted even if it's just "installed", without being "authorized".
Verifying your identity is needed so that only you can view links to private repositories and your organizations. Other things, well, the service is not even asking for.
Feel free to revoke this part (but keep the install) when you're done with this website's UI.
An exhaustive list of what this service stores:
The server of the main instance also keeps access logs and application logs for up to 3 months.
This page will be updated if this changes.
No paid features are currently planned.
This service is developed and run by Oleh Prypin.
It has no affiliation with my employer. No affiliation with GitHub either.
Open an issue at https://github.com/oprypin/nightly.link/issues
The source code is available in a Git repository at https://github.com/oprypin/nightly.link
Copyright (C) 2020 Oleh Prypin
This program is free software: you can redistribute it and/or modify it under the terms of the GNU Affero General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Affero General Public License for more details.
You should have received a copy of the GNU Affero General Public License along with this program. If not, see https://www.gnu.org/licenses/.