Add redirects for the 404s left after #63 - #64
Merged
Conversation
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughAdded twelve GitBook redirects for CI integrations, CLI and Cypress documentation, rerun orchestration, Jira, projects, webhooks, and Currents Actions. ChangesDocumentation redirects
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
Suggested labels: ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![baz-app[bot]](https://avatars.githubusercontent.com/in/1124379?s=60&v=4){kind=small}
Search Console lists 91 crawled 404s on docs.currents.dev. #63 covers ten of the ones that are real page moves; these twelve are the remainder, including every path still reachable from currents.dev/readme/*. Four are bare CI-provider paths (ci-setup/circleci, ci-setup/azure-devops, ci-setup/bitbucket, ci-setup/jenkins-playwright) that predate flattening the ci-setup tree. Files with those names still exist at the repo root but are absent from SUMMARY.md, so GitBook does not serve them — hence the 404. Adding redirects is additive and leaves those files alone; whether the unlisted ci-setup/ directory should exist at all is a separate question. The rest are single pages that moved section: currents-cli to resources/reporters, jira to resources/integrations, currents-actions and the orchestrated re-run guide to their current homes. Every target verified to return 200 on docs.currents.dev, and every target file verified to exist on disk. 79 entries total, no duplicate keys. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013vBAvmWyyJsE1eTnxXL2XP
agoldis
force-pushed
the
fix/redirect-map-gaps
branch
from
August 8, 2026 08:13
4af2f1e to
beadfd0
Compare
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
1 participant
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.
User description
What
Twelve
.gitbook.yamlredirect entries for URLs that still hard-404.Why
Search Console reports 91 crawled 404s on
docs.currents.dev. #63 already covers ten that are real page moves. These are the remainder — including every path still reachable fromcurrents.dev/readme/*, which is being converted from a proxy rewrite to a 301 in currents-dev/www.currents.dev#250.Bare CI-provider paths (4) — predate flattening the
ci-setuptree:Files with those names still exist at the repo root but are absent from
SUMMARY.md, so GitBook doesn't serve them — which is why they 404. These entries are additive and leave the files alone. Whether that unlistedci-setup/directory should exist at all is a separate question;ci-setup/jenkins-playwright.mdis 76 lines of real content, so I didn't touch it.Pages that moved section (8) —
currents-clitoresources/reporters,jiratoresources/integrations,currents-actionsand the orchestrated re-run guide to their current homes, plusprojects,webhooks,actions.Verification
Every target URL returns 200 on
docs.currents.dev:YAML parses. All 79 targets exist on disk. No duplicate keys.
Not fixed here — 60 of the 91 docs 404s are a GitBook bug
Two-thirds of the docs 404s are
<page>/rss.xml. GitBook emits this on every page:No feed exists at that path, or at
/rss.xml. Google follows the link and records a 404, once per page. Nothing in this repo controls that markup — it needs a GitBook support ticket, not a redirect.🤖 Generated with Claude Code
https://claude.ai/code/session_013vBAvmWyyJsE1eTnxXL2XP
Generated description
Below is a concise technical summary of the changes proposed in this PR:
Add twelve GitBook redirect entries to route remaining hard-404 documentation URLs to their current pages. Update the
.gitbook.yamlredirect configuration to cover relocated CI setup, integration, dashboard, reporter, and guide content while preserving existing source files.projects,webhooks, andactionsto their current dashboard, integration, and guide locations.Modified files (1)
Latest Contributors(2)
currents-cli, Jira, Cypress compatibility, parallelization, and rerun guides.Modified files (1)
Latest Contributors(2)
Summary by CodeRabbit