Repository navigation
Fixture README: every fixture with size and generator - #5
Merged
Merged
Conversation
Tests/Fixtures/README.md lists every committed fixture with size and the tools/ script that names it; rows found only by name prefix are marked. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017hJFgt7ZpMGSUej75yY3u7
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 Paul · project thread
Adds
Tests/Fixtures/README.md(docs only, no Sources or Package changes): one row per committed fixture (152), with size and thetools/script that names it. Rows matched only by file-name prefix, tool-folder name or test module say so. 5 fixtures no script names are listed under "Needs an origin line" for a Mac session to fill in with the pin scripts.Owner data: none found. A search of every committed fixture (text and binary) for
/Users/,paullobpreisandLobpreiscame back empty; no file was moved.Docs workflow, finding for Paul. The 0.8.1 tag run of
docs.ymlbuilt the site fine (build job green, 2 min); onlydeployfailed, after 1 second with no steps run. That pattern is thegithub-pagesenvironment refusing the tag ref, not the workflow file: GitHub creates that environment with a rule that allows deployment frommainonly. The fix is a setting, not a code change: Settings > Environments > github-pages > Deployment branches and tags > add a tag rule*(or all tags). Also confirm Settings > Pages > Source is "GitHub Actions". I could not read the job log (404), so this is the likely cause, not a confirmed one; re-run the deploy job after the change to check.Generated by Claude Code