Repository navigation
ci(public): catch broken Getting Started, support and landing links before merge - #318
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 05baee72d9
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| if url.fragment and unquote(url.fragment) not in sections: | ||
| issues.append(f"index.html: missing section {raw}") |
There was a problem hiding this comment.
When a landing-page link includes both a local path and a fragment, this checks the fragment against IDs in index.html rather than anchors in the linked document. Consequently, a valid link such as docs/INSTALL.md#windows fails even when that target contains a Windows heading, while a broken destination fragment can pass if its name happens to match a landing-page ID. Restrict the current sections check to same-page links and validate cross-document fragments against the resolved target.
Useful? React with 👍 / 👎.
Adds a zero-dependency Python acceptance gate for local links in user-facing README, Getting Started, Support, Studio, feature matrix and developer index; also checks product page section anchors. Runs on relevant PRs and pushes. It complements the existing live-browser/release tests, without changing runtime, firmware, release binaries or user-facing claims. The gate permits optional guides not yet on main; after #316 lands it checks them automatically. Merge after the GitHub Actions check passes.