Skip to content

docs(readme): move the rich version from the hero to Usage - #112

Merged
umiyosh merged 2 commits into
masterfrom
docs/readme-hero-usage
Nov 18, 2026
Merged

umiyosh merged 2 commits into
masterfrom
docs/readme-hero-usage

Conversation

@umiyosh

@umiyosh umiyosh commented Nov 18, 2026 •

Copy link
Copy Markdown
Owner

Summary

The top of both READMEs now shows only what motion-render does, one request, and the demo video. How to ask for a film cut to the beat moves to Usage, under a new subsection ("Films cut to the beat: the rich version" / "音ハメの動画: rich 版").

Moved as is, with no change to the text: the rich request, its paragraph, the comparison table, and the note that the default works like 1.1. The bold lead line is replaced by the subsection heading.

CI fix (#113)

CI failed twice on this PR with every test passing: [vitest-worker]: Timeout calling "onTaskUpdate". The error came right after tests/type.test.ts (142.7 s, the longest file). Two of its tests ran the check command 12 and 6 times in a row with spawnSync, which blocks the worker so it cannot report to vitest. passesCheck now runs the command with spawn and is awaited, as the file's differ already did for ffmpeg.

Fixes #113.

Test plan

  • prettier --check README.md README.ja.md passes
  • The README diff only moves lines (36 removed, 36 added in each file)
  • make check passes locally: 34 files, 282 tests
  • CI passes

@umiyosh
umiyosh merged commit a60f1f7 into master Nov 18, 2026
1 check passed
@umiyosh
umiyosh deleted the docs/readme-hero-usage branch November 18, 2026 18:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ci: the coverage job fails with vitest's 'Timeout calling onTaskUpdate' while every test passes

1 participant