mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-08 19:56:53 +00:00
kevinveenbirkenbachandClaude Opus 5
fcc98bcad1
The lint accepted a link that resolved to a file or a directory. myst builds a document reference only when the target is_file(), so a link to a directory without a README is a bare file listing on GitHub and a dead cross-reference in the documentation build. It now reports which of the two reasons applies. The tightened rule found 41 links. Where a README backs the directory, bd15eae9fa's resolver carries the link and it stays. Where none exists, the link becomes a code span rather than an invented README: 15 of them point at a role's meta/addons/, whose addon table already sits below the sentence, and the rest at code directories such as utils/ or cli/administration/deploy/runner/. The changed sentences are msgids, so these entries return to the translator on the next extract. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
927 B
927 B
Pull Requests
- You MUST choose the matching Pull Request template before you write a PR description.
- You MUST follow the template selection guidance in CONTRIBUTING.md.
- You MUST use the templates from
.github/PULL_REQUEST_TEMPLATE. - You MUST treat the selected template as the SPOT for PR structure, author input, and review context.
- PRs MUST target the canonical repository that https://s.infinito.nexus/code redirects to, unless the operator explicitly names a different target. Before creating the PR, the agent MUST resolve the redirect (e.g.
curl -sSIL https://s.infinito.nexus/code | grep -i '^location:') to obtain the canonical repository URL, then compare it againstgit remote get-url origin. If the two do not point to the same repository (host + owner + repo, ignoring.gitsuffix andhttps://vs.git@scheme), stop and ask the operator before creating the PR.