The repository's own gates had no runner (GitHub-hosted ci.yml). Ported:
lint.yaml: markdownlint (repo config), yamllint over all YAML, offline lychee internal-link check (pinned musl build, sha256);
windows.yaml: conformance self-test, fuzzing, package tests, static self-conformance (-Repository given, since the runner's checkout directory is not named after the repo).
.yamllint.yaml: default rules except line length, which K22-CODE-08 leaves unlimited. The published .github reusable workflows are untouched.
Proven green with the caller on ci-workflows@main (run 7223); the last commit pins @v1, which runs once the owner moves v1 to include the new workflow.
The repository's own gates had no runner (GitHub-hosted `ci.yml`). Ported:
- `lint.yaml`: markdownlint (repo config), yamllint over all YAML, offline lychee internal-link check (pinned musl build, sha256);
- `windows.yaml`: conformance self-test, fuzzing, package tests, static self-conformance (`-Repository` given, since the runner's checkout directory is not named after the repo).
`.yamllint.yaml`: default rules except line length, which K22-CODE-08 leaves unlimited. The published `.github` reusable workflows are untouched.
Proven green with the caller on `ci-workflows@main` (run 7223); the last commit pins `@v1`, which runs once the owner moves `v1` to include the new workflow.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
The repository's own gates had no runner since the GitHub-hosted
ci.yml cannot run on Gitea. Port them to the shared ci-workflows:
- lint.yaml: markdownlint (repo config), yamllint over every YAML
file, and the offline lychee internal-link check (pinned, sha256);
- windows.yaml: the conformance checker self-test, fuzzing, package
tests and the static self-conformance check.
.yamllint.yaml keeps every default rule except line length, which
K22-CODE-08 leaves unlimited.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The gnu lychee needs glibc 2.38, newer than the lint image's. The runner
checks out into a directory named after the runner user, so the static
check must be told the repository name (K22-REPO-42 looks it up in
MAINTAINERS.md).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The repository's own gates had no runner (GitHub-hosted
ci.yml). Ported:lint.yaml: markdownlint (repo config), yamllint over all YAML, offline lychee internal-link check (pinned musl build, sha256);windows.yaml: conformance self-test, fuzzing, package tests, static self-conformance (-Repositorygiven, since the runner's checkout directory is not named after the repo)..yamllint.yaml: default rules except line length, which K22-CODE-08 leaves unlimited. The published.githubreusable workflows are untouched.Proven green with the caller on
ci-workflows@main(run 7223); the last commit pins@v1, which runs once the owner movesv1to include the new workflow.🤖 Generated with Claude Code