Ludovic Marie
48c85fa19f
pr_ready is the one self-check to run before asking for review: from the files a branch changes it runs rustfmt, clippy with warnings denied, the tests of the touched crates (mapped through cargo metadata), the launcher's own workspace when it is affected, the tokens.css check, the Cargo.lock rule, the Python tests and the public-tree check, and the vanilla harnesses the change can affect, picked by tools/parity.py exactly as CI's parity job picks them. It runs locally or on a fleet machine through ~/fleet/rbuild; on the Mac mini the harnesses use the parity runner's own workspace and scripts. It prints one Markdown block for the pull request body and exits non-zero on any failure. tools/parity.py gains --changed-files for copies without Git history, and tools/ci/vanilla-data.sh accepts the preparation key from outside. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
20 lines
660 B
Markdown
20 lines
660 B
Markdown
## What and why
|
|
|
|
<!-- What this changes, and why. Link the issue it fixes ("Fixes #123"). -->
|
|
|
|
## Vanilla reference
|
|
|
|
<!-- The vanilla classes and methods this follows (tools/rea_vanilla.py), and the harness that checks it.
|
|
"Horizon-only" for a feature vanilla doesn't have; "none" for tooling or docs. -->
|
|
|
|
## Self-check
|
|
|
|
<!-- Paste the block `python3 tools/pr_ready.py` prints (`--base upstream/main` from a fork). -->
|
|
|
|
## Screenshots
|
|
|
|
<!-- For anything players see: before and after. Delete this section otherwise. -->
|
|
|
|
<!-- Please tick "Allow edits by maintainers": we push small fixups ourselves instead of a round trip.
|
|
See CONTRIBUTING.md. -->
|