Skip to content

Clean up .vale.ini before deslop validation harness#1535

Closed
justinegeffen wants to merge 12 commits into
masterfrom
justine-vale-config-cleanup
Closed

Clean up .vale.ini before deslop validation harness#1535
justinegeffen wants to merge 12 commits into
masterfrom
justine-vale-config-cleanup

Conversation

@justinegeffen

Copy link
Copy Markdown
Contributor

Summary

Tidies .vale.ini ahead of running the deslop validation harness so the production config doesn't muddy measurements. Pure cleanup — no behaviour change in CI's vale-lint job, plus one incidental bug fix.

  • Collapses duplicate [*.md] and [*.mdx] sections into a single [*.{md,mdx}] glob so any future override only needs to be edited once.
  • Consolidates the two BlockIgnores directives into a single comma-separated line. In the old config these lived inside the [*.mdx] section, so .md files weren't ignoring code fences or frontmatter at all. Moving them up to the section glob fixes that incidentally.
  • Drops Packages = write-good in favour of the vendored copy under .github/styles/write-good/. errata-ai/vale-action still calls vale sync inside its container, but the vendored copy keeps local and CI output deterministic without depending on the Vale hub being reachable.
  • Removes a misleading trailing comment claiming .vale.ini configures paths — Vale takes paths from the CLI invocation.

Verification

  • vale ls-config parses the new file cleanly; BlockIgnores, TokenIgnores, RuleToLevel, and SBaseStyles all resolve as expected for *.{md,mdx}.
  • vale --no-exit platform-cloud/docs/quickstart.md still surfaces the expected Seqera.Features errors (e.g. configconfiguration) and write-good.E-Prime / Passive / TooWordy suggestions.

Test plan

  • Comment /editorial-review on a PR with doc changes and confirm the vale-lint job in docs-review.yml still posts the same inline review output.
  • Confirm no new findings appear for .md files that weren't there before (the BlockIgnores move means code fences and frontmatter in .md files are now ignored — net reduction in noise, not new errors).

🤖 Generated with Claude Code

- Collapse duplicate `[*.md]` and `[*.mdx]` sections into `[*.{md,mdx}]`
- Consolidate two `BlockIgnores` directives into a single line, and move
  them under the section glob so `.md` files also ignore code fences and
  frontmatter (previously only `.mdx` did)
- Drop `Packages = write-good` so the vendored copy under
  `.github/styles/write-good/` is the source of truth instead of the Vale
  hub. CI still runs `vale sync` via errata-ai/vale-action; the vendored
  copy keeps local + CI output deterministic and aligned
- Remove the misleading trailing comment about "paths to check" — Vale
  takes paths from the CLI invocation, not `.vale.ini`

Verified `vale ls-config` parses cleanly and that linting a sample .md
file still surfaces the expected Seqera and write-good findings.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@netlify

netlify Bot commented Jun 8, 2026

Copy link
Copy Markdown

Deploy Preview for seqera-docs ready!

Name Link
🔨 Latest commit 82fc784
🔍 Latest deploy log https://app.netlify.com/projects/seqera-docs/deploys/6a30cbc474d74b0008a1f2d5
😎 Deploy Preview https://deploy-preview-1535--seqera-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

justinegeffen and others added 2 commits June 8, 2026 11:08
- Drop platform-enterprise_versioned_docs from the Vale file list.
  Versioned docs are frozen snapshots; findings there are noise that
  reviewers can't act on without editing a release archive.
- Flip fail_on_error from false to true. The Seqera substitution rules
  (Tower → Seqera Platform, etc.) are declared at level: error in
  .github/styles/Seqera/*.yml. Leaving fail_on_error: false meant the
  declared severity was purely cosmetic — terminology errors posted as
  comments but never gated merges. With fail_on_error: true the gate
  matches the configured severity.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Previously Vale only ran when a contributor commented /editorial-review
on a PR — the same on-demand path used for the LLM editorial review.
Vale is fast, cheap, and deterministic; it should run on every PR push
without anyone opting in.

- New workflow .github/workflows/vale.yml triggers on pull_request when
  doc files, styles, or .vale.ini change. Same scope and same
  fail_on_error: true configuration as the previous job (which was
  already adjusted on this branch).
- Remove the vale-lint job from docs-review.yml and the summary
  references to it. docs-review.yml is now LLM-only.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@justinegeffen justinegeffen added the do not merge Do not merge until this label is removed label Jun 10, 2026
justinegeffen and others added 5 commits June 10, 2026 11:28
write-good was referenced in BasedOnStyles but no longer vendored or
fetched via `vale sync`, which broke CI with "style 'write-good' does
not exist on StylesPath". The only active rule it contributed was
Passive at suggestion level, which the editorial-review agents already
cover.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@justinegeffen justinegeffen deleted the justine-vale-config-cleanup branch June 17, 2026 08:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do not merge Do not merge until this label is removed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants