Fix dead Chakra UI, PublicTechnology, and Sphinx doc links - #4
Closed
olitreadwell wants to merge 3 commits into
Closed
Fix dead Chakra UI, PublicTechnology, and Sphinx doc links#4olitreadwell wants to merge 3 commits into
olitreadwell wants to merge 3 commits into
Conversation
olitreadwell
force-pushed
the
docs/fix-chakra-style-props-link
branch
from
August 18, 2026 22:43
2d4e810 to
e482b4c
Compare
Owner
Author
|
Reopening to refresh PR base against the synced fork default (removes upstream commits from the diff). |
- The link to Chakra's style props docs 404s: chakra-ui.com restructured its docs site and dropped the old /docs/features/style-props path. - frontend/package.json pins @chakra-ui/react to ^2.8.2, so point the link at the matching v2 docs site instead, where the page still exists (verified 200, title 'Style Props - Chakra UI').
The old URL used a percent-encoded curly-quote slug (articles/features/interview-singapore...) that now 404s. PublicTechnology migrated to a date-based URL scheme; the article now lives at /2019/07/26/international-relations/... with a plain ASCII slug. Verified the new URL returns 200 and the page title matches the original article exactly.
The pinned Sphinx 3.x docs (index and installation instructions) have been removed from readthedocs.org and now return a "Documentation version not found" 404. Point both links at the master version instead, matching the existing master-pinned link further down in the same file (sphinx-build.html), which already resolves.
olitreadwell
force-pushed
the
docs/fix-chakra-style-props-link
branch
from
August 19, 2026 00:25
e482b4c to
0ec7d90
Compare
Owner
Author
|
Closing as duplicate: the same change was already submitted upstream in canada-ca#7506 (CLOSED). See canada-ca#7506 |
Owner
Author
|
Superseded by upstream canada-ca#7506. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this PR does
Fixes a dead link in
frontend/README.md: the Chakra UI 'style props' doc link 404s.Verification:
curl -sL -o /dev/null -w '%{http_code}' https://chakra-ui.com/docs/features/style-props->404(chakra-ui.com restructured its docs; the old/docs/features/style-propspath is gone: confirmed with a real HTTP request, not a bot-block: plain 404, no Cloudflare challenge page).frontend/package.jsonpins@chakra-ui/reactto^2.8.2, so the canonical replacement is the version-matched v2 docs site:https://v2.chakra-ui.com/docs/styled-system/style-props->200, page title confirmed as "Style Props - Chakra UI".One logical change, one line changed.
Policy passport (canada-ca/tracker)
canada-ca/.githubcommunity-health repo (404): repo-level CONTRIBUTING is authoritative, no org defaults to merge infix(dns-scanner): ..., this PR follows withdocs(frontend): ...Fork-internal, non-draft
Base is this fork's own default branch (master), never upstream canada-ca/tracker.
AI disclosure
This PR was prepared with AI assistance (an agentic coding tool) under my direction; I will review it myself before promoting anything upstream.
No AI-use policy or disclosure checkbox was found in this repo or a would-be org default, so there is no box to leave unticked: this note is the disclosure.
Promotion (manual, not automated)
To open this against upstream once reviewed:
gh pr create --repo canada-ca/tracker --base master --head olitreadwell:docs/fix-chakra-style-props-link-20260805-004827
No CLA, no DCO sign-off, no issue-first requirement, and no signed-commit requirement were found: nothing blocks promotion as-is.
CI status
This repo's substantive test/lint/build CI runs externally on Google Cloud Build (see the
gcbruncheck and thenorthamerica-northeast1-docker.pkg.dev/track-compliance/tracker/...image tags in the commit history): not connected to forks.The only GitHub Actions wired here are CodeQL security scanning, a Dependabot Cloud Build trigger, and a maintenance-mode toggle; none of them ran against this PR (CodeQL did not trigger on the fork).
There is no code to lint/build/test: this is a single-line markdown link fix.
Verdict: locally-verified (link checked with real
curlrequests, not fork-CI-green), per this project'sexternal_ci_providerhandling.All commits in this PR
This PR bundles 3 related fixes (same repo, same trivial-fix theme: broken links / typos / stale references), per the story-PR consolidation policy:
How to verify
git fetch https://github.com/olitreadwell/tracker.git docs/fix-chakra-style-props-link git checkout FETCH_HEAD curl -sL -o /dev/null -w '%{http_code}' https://chakra-ui.com/docs/features/style-propsAI assistance
Drafted with AI assistance.
The gap was found and verified against the current code, the change was verified before opening, and this diff was reviewed line by line.
PROMOTION NOTE (remove this section before/when opening against upstream):
Prerequisites: none outstanding (re-verify CLA/DCO/signing before promoting).