Skip to content

docs(agents): require lychee local-run on every PR — added to Before submitting#411

Merged
potiuk merged 2 commits into
apache:mainfrom
potiuk:docs-agents-run-lychee-before-pr
May 31, 2026
Merged

docs(agents): require lychee local-run on every PR — added to Before submitting#411
potiuk merged 2 commits into
apache:mainfrom
potiuk:docs-agents-run-lychee-before-pr

Conversation

@potiuk

@potiuk potiuk commented May 31, 2026

Copy link
Copy Markdown
Member

Summary

Add a Before-submitting checklist entry that requires running `lychee --config .lychee.toml .` locally on every PR. Caught a Fragment-not-found regression in PR #410 only after CI flagged it; the check is cheap to run locally and catching it before the push avoids a round-trip.

Change

Append to the existing Before submitting checklist in `AGENTS.md`:

  1. The canonical invocation (matches the CI workflow).
  2. A note on the most common failure class — `Fragment not found in document` — which is exactly what bites on doc refactors that move sections between files or rename headings (the class that just bit PR refactor(security-issue-sync): extract 4 subdocs to slim SKILL.md 3425 → 658 lines #410).
  3. A one-liner workaround for v0.24+ local lychee installs, since `.lychee.toml` pins the v0.23 schema for CI compatibility.

The rule is enforced by CI either way (the lychee workflow blocks merge on any failure); this just makes the local check a documented pre-push habit so agents avoid the CI round-trip.

Test plan

  • AGENTS.md renders cleanly (table of contents intact, no broken links introduced by this edit)
  • Next PR opened against the framework after this lands has the lychee local-run done before push (verified by absence of doc-refactor-induced fragment errors on CI)

🤖 Generated with Claude Code

potiuk added 2 commits May 31, 2026 12:48
…submitting

Caught a Fragment-not-found regression in PR apache#410 only when CI
flagged it. The check is cheap to run locally (offline file + fragment
lookups; only the external-URL subset hits the network) and catching
it before the push avoids a round-trip.

Add to the Before-submitting checklist:

- the canonical invocation (lychee --config .lychee.toml .)
- guidance on the most common breakage class (Fragment not found)
  which is what bites on doc refactors that move sections between
  files or rename headings
- a one-liner for v0.24+ local lychee installations (since .lychee.toml
  pins the v0.23 schema)

The rule is enforce-via-CI either way (the lychee workflow blocks the
merge on any failure); this is just a documentation reminder so
agents add it to their pre-push routine and avoid the round-trip.
…n.yml

The "Before submitting" lychee guidance pointed at
`.github/workflows/doc-validation.yml`, which does not exist —
this repo's link-check workflow is `link-check.yml`. Caught by
running lychee on the same file the PR added (which is what the
new rule itself prescribes).
@potiuk potiuk merged commit 895477f into apache:main May 31, 2026
16 checks passed
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.

1 participant