GitHub Documentation Link Auditor

Read selected Markdown files through an Apify GitHub MCP connector, validate their public external links, and create or update one evidence-rich GitHub issue without cloning the repository or handling a GitHub token.

Why the connector matters

The Actor receives authorized connectors, not a personal access token. Dry runs need only a read connector exposing get_file_contents. Write mode adds a second connector exposing only search_issues and issue_write. Neither connector can edit repository files, create a branch, open a pull request, or merge code; the same Apify connector resource may be selected for both inputs when it has all three tools.

Failure-aware classification

• reachable: final HTTP 2xx/3xx response.
• observed_not_found: one time-stamped HTTP 404 or 410 observation that still requires human confirmation.
• needs_review: authentication, rate limiting, DNS/network errors, 4xx other than 404/410, or 5xx.
• unsafe_target: rejected before a request because the URL contains credentials, uses a non-standard port, or resolves to loopback/private/link-local/reserved infrastructure.

Every redirect target is normalized, resolved, and checked again before it is requested. A custom resolver pins the actual connection to the public IP addresses that passed validation while preserving the original hostname for TLS verification. Environment proxies are disabled. The Actor streams response headers and does not download response bodies.

Safe operating model

Dry run is the default. To post an issue, disable dry run and enter the exact owner/repo in confirmWriteTarget. The Actor writes at most one issue per run and updates only an issue containing its invisible ownership marker. A human-authored title collision is never overwritten. Human review remains mandatory before changing documentation.