Repository navigation
fix(docs-site): stop redirecting the live auth and migration pages - #3803
Merged
Merged
Conversation
/getting-started/authentication and /getting-started/migration are maintained pages, but legacy redirects shadowed them: the deployed site sent readers to consumer/authentication and troubleshooting/migration. Both of those link back to the getting-started page as the deep guide, so the link loops, and CLI auth errors point users at anchors such as getting-started/authentication/#on-prem-azure-devops-server that never render. Drop the two redirects so the pages build again. Refs #3800 Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Daniel Meppiel (danielmeppiel)
requested a review
from Sergio Sisternes (sergio-sisternes-epam)
as a code owner
November 17, 2026 20:12
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
No active review issues were identified for the documentation redirect removal.
No open issues 🎉
What changed in this PR
Restores access to the maintained authentication and Existing Projects guides by removing legacy redirects that shadow their routes. This addresses one routing issue from the documentation re-sweep in #3800.
Changes:
- Removes the authentication redirect so the full guide and its linked anchors can render.
- Removes the migration redirect so the Existing Projects page can render, without changing sidebar placement.
| File | Description |
|---|---|
docs/astro.config.mjs |
Removes two redirects that override maintained getting-started pages. |
Review effort: Balanced
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.
Description
getting-started/authentication.md(the full token-resolution guide) andgetting-started/migration.md("Existing Projects") are maintained pages, but two legacy redirects indocs/astro.config.mjsshadow them. On https://microsoft.github.io/apm/ both URLs redirect away (the build warnsCould not render /getting-started/authentication ... conflicts with higher priority route):/getting-started/authentication->/consumer/authentication, whose "Going further" section links back to the getting-started guide: a loop. CLI auth errors (src/apm_cli/core/auth.py) send users togetting-started/authentication/#on-prem-azure-devops-serverand similar anchors, which never render. About ten pages link to the guide as the deep reference./getting-started/migration->/troubleshooting/migration, which tells readers to "start with Existing Projects" at the getting-started URL: same loop.This change removes the two redirects so the pages build and serve again. Sidebar placement is unchanged.
Issue and approved scope
Issue: Refs #3800
Human scope-approval comment: #3800 (comment)
Does this PR complete the issue, or what remains? Partial: one finding from the corpus re-sweep. Other area fixes land in separate PRs.
Type of change
Testing
cd docs && npm ci && npm run buildexits 0; "All internal links are valid"; "Checked 1191 relative link(s) ... No broken relative links found".dist/getting-started/authentication/index.htmlanddist/getting-started/migration/index.htmlnow render the page titles instead of a meta-refresh, and the route-conflict warnings for both pages are gone.Spec conformance (OpenAPM v0.1)