chore: move docs/vista-lint-presets/ → examples/vista-lint-presets/ - #9
Merged
rafael5 merged 1 commit intoMay 11, 2026
Merged
Conversation
Copy link
Copy Markdown
Collaborator
Sorry, something went wrong.
Part of a cross-repo cleanup making `docs/` hold only human-readable prose. The vista-lint-presets directory contains a copy-paste TOML config preset (`m-cli.toml.example`) alongside a README explaining it — that's a worked-example artifact, not documentation prose. Aligns m-cli's layout with m-stdlib (which uses `examples/` for demos like `stdargs-demo.m`). Self-reference inside m-cli.toml.example updated to point at the new README path and at m-stdlib's relocated docs/testing/ subdir. Cross-repo inbound references in m-stdlib's templates/m-vista-test-suite/ + docs/testing/vista-corpus-lint-results.md will be fixed in a separate m-stdlib PR once this lands.
rafael5
added a commit
that referenced
this pull request
May 11, 2026
Adds make check-docs-prose as a cross-repo guardrail: docs/ holds only human-readable prose (.md, .markdown, images, .gitkeep). Non-prose artifacts — generated data, JSON/TSV output, copy-paste examples, scaffolding templates — belong under dist/, examples/, templates/, or a top-level domain-specific directory. Wires into CI alongside the existing manifest drift gate. Engine-free, fast, find-based. Currently green (docs/ is already prose-only after PR #9 moved vista-lint-presets to examples/) — this is preventive, not corrective.
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.
Summary
Part of a cross-repo cleanup: docs/ should hold only human-readable prose. The vista-lint-presets/ directory contains a copy-paste TOML config preset (m-cli.toml.example) alongside a README explaining it — that's a worked-example artifact, not documentation prose.
The move also aligns m-cli's layout with m-stdlib (which already uses examples/ for demos like stdargs-demo.m).
Changes
No src/ or tests/ code touches the path. The other reference inside m-cli.toml.example to m-stdlib/docs/vista-corpus-lint-results.md was also corrected to the actual docs/testing/ subdir where that file currently lives.
Cross-repo follow-up (separate PR)
m-stdlib has three inbound references that will need updating once this lands: