Repository navigation
chore: a report index per branch, for the site to find the reports - #3
Merged
Merged
Conversation
- report.sh writes reports/index.json: every report of the branch with its last run (result, start, tests, coverage, time), newest first - the site reads the reports from raw.githubusercontent.com, which cannot list a folder, so it starts from the index
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.
report.shalso writesreports/index.json: each report of the branch with its last run, newest first. The site at dnsk.sawking.tech reads reports from raw.githubusercontent.com, which cannot list a folder, so it needs the index.Checked locally on
reports/offull: one entry, v2.6.1, 2 runs, last success with 358 tests.🤖 Generated with Claude Code
https://claude.ai/code/session_01Uhup8cKanyPsTah73ZMAZ3