ci: upload download link audit results as an artifact - #1998
Merged
Conversation
MarshallOfSound
approved these changes
Aug 6, 2026
MarshallOfSound
marked this pull request as ready for review
August 6, 2026 21:55
dsanders11
approved these changes
Aug 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requested by Samuel Attard · Slack thread
Before: the results of the nightly download-link check (the broken-links table or the "no broken links" note) only exist on the workflow run's step summary page, which is not retrievable through any GitHub API — so automated tooling and agents cannot read the findings.
After: the same findings markdown is also uploaded as a build artifact named
audit-results, downloadable via the GitHub API. The upload usesarchive: false, so the artifact is a single raw file listed under the file nameaudit-results.md, and the REST artifact endpoint serves the raw markdown directly — no zip extraction needed. The step summary, exit code, and all other behavior are unchanged.How: immediately before
await core.summary.write()(which empties the summary buffer), the script writes the buffered markdown toaudit-results.mdviacore.summary.stringify(). A newactions/upload-artifactstep (pinned to the same SHA the repo already uses inrelease.yml, v7.0.1) uploads that file witharchive: falseandif: always()so the artifact is produced whether or not broken links were found and the step failed.Generated by Claude Code