Repository navigation
Conversation
A new job reads the report artifacts the test jobs already upload and publishes them as one page, https://pages.flisk.si/@parcels-code/test-reports/, so they can be read without downloading a zip. It runs on pushes to main only, needs only id-token: write (no secret), and runs none of this repository's code. Signed-off-by: odykyi <odykyi@users.noreply.github.com>
This comment was marked as spam.
This comment was marked as spam.
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.
Description
Adds one CI job that publishes the pytest-html reports the test jobs already upload as a page, https://pages.flisk.si/@parcels-code/test-reports/, so a report can be read in the browser without downloading and unzipping an artifact. It is an option: no existing job is changed.
main; it is skipped onpull_request(checked on a fork, see below).id-token: write, on that job. pages.flisk.si checks the run's OIDC token to know the repository, so there is no secret.pattern: "* report *") and runs none of this repository's code.flisk-sh/pagesandactions/download-artifactare pinned by SHA.continue-on-error: trueon the publish step, so an outage of pages.flisk.si never turnsmainred.Proof on my fork (a full CI run on
main, with one deliberately failing test that is not part of this PR): https://github.com/odykyi/Parcels/actions/runs/41311255247. The job passed ("Checked and committed as version 3", "Live now"), your zizmor job passed with the new job in it, and the page shows the failing test. A pull request on the fork skipped the job: https://github.com/odykyi/Parcels/actions/runs/41309431699. Full evidence with screenshots and raw logs is in the first comment below.Checklist
mainfor normal development,v3-supportfor v3 support)AI Disclosure
I work on Flisk / pages.flisk.si, so I have an interest in this. It is a small, opt-in change; close it if you'd rather not.
Not verified: the job has not run in
Parcels-code/Parcelsitself, so@parcels-code/test-reportsis untested; behaviour when many projects publish at once (the site's deploy takes minutes under load, the job waits up to 10 minutes then only warns); a failed run that never uploads a report would fail the new job too (the same red run, one more red job).[This is Claude Code on behalf of odykyi]
🤖 Generated with Claude Code