Repository navigation
chore: each branch keeps its reports in reports/<branch>/ - #4
Merged
Merged
Conversation
- report.sh writes reports/<branch>/<version>.json, .md and index.json, so merging two sample branches keeps the reports of both - reports an earlier run left directly in reports/ move into the branch's folder on the branch's next report; the old index is dropped and rebuilt - the README of the samples names the folder
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
1 participant
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.
Every sample branch had reports/index.json and reports/v2.6.1.json under the same names, so merging two branches would overwrite one branch's reports or conflict.
Checked on a clone of single with CI run 37160566570: reports/index.json, v2.6.1.json and v2.6.1.md moved to reports/single/, the index lists v2.6.1 with 279 tests and 64.4% line coverage.
The site reads reports//index.json after the matching change in DotNetSolutionKit.
🤖 Generated with Claude Code
https://claude.ai/code/session_01NczLWHuimhqeSmGQ2jjX8X