test: Example PR that fails the redirect check (do not merge)

[marcleblanc2]

Example for the docs-maintainer announcement: one PR, one failing check. Do not merge.

Adds four entries to src/data/redirects.ts, each breaking one rule: the source shadows a page that exists, a /docs prefix, a redirect whose destination is another redirect, and a destination page that does not exist. The Check redirects workflow should comment a report and suggest fixes for the two it can fix.

Built on main plus #1935 (marc/check-redirects, rebased) because the check is not on main yet, so the diff also shows the check's own files. The last commit is the example; once #1935 merges, only that commit remains.

Siblings: #1963 spell check and #1964 link check. Replaces the all-in-one #1948 for the announcement.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
sourcegraph-docs	Ready	Preview	Sep 15, 2026 9:08pm UTC

[github-actions]

❌ This PR breaks 4 redirect(s)

Redirects are used so inbound traffic from external sources (links inside old versions of our product, bookmarks, search results, etc.) to old doc pages still reaches a relevant page.

A correct entry maps the old page path, exactly as the browser requests it, straight to a page that exists today, with an optional #heading that exists on the destination page:

{
	source: '/old/section/page',
	destination: '/new/section/page#heading-slug'
},

Each section below explains how to fix the entries listed under it.

Do not use redirects for broken internal links, internal links must be fixed properly to tame the tech debt snowball no one wants to deal with; the "Check links" PR check comment lists the links this PR broke, if any.

src/data/redirects.ts

Source overshadows a docs page that exists

Redirects take precedence over pages, so visitors to that page's URL are redirected away from it. Update or remove the redirect or the page to remove the conflict.

• line 5

  source: '/code-ownership',
  destination: '/code-ownership/codeowners-format'

Source or destination starts with /docs

Write paths without the /docs prefix. The site removes /docs from the requested URL before matching sources, and adds it back in front of the destination, so a /docs/... source never matches and a /docs/... destination lands on /docs/docs/....

• line 9

  source: '/docs/ownership',
  destination: '/code-ownership'

  Fix: change the source to /ownership

Destination is another redirect

Chained redirects cost the customer's browser a round trip, slow down their page load time, and frustrate them. They also make the redirects file impossible to maintain, and make it too easy to create redirect loops. Change the rule's destination to the final destination.

• line 13

  source: '/ownership/tls',
  destination: '/admin/tls_ssl'

  Fix: change the destination to /self-hosted/http-https-configuration

Destination page does not exist

Set the redirect destination to the page that replaced it, or remove the rule if there is no replacement page; visitors then get our fancy 404 page, with links they can click to find where they're trying to go, and the search bar.

• line 17

  source: '/ownership/guide',
  destination: '/code-ownership/guide'

Reproduce locally with node dev/check-redirects.mjs

[github-actions]

Problem: Source or destination starts with /docs
Fix: change the source to /ownership

Suggested change

	{
	source: '/docs/ownership',
	destination: '/code-ownership'
	},
	{
	source: '/ownership',
	destination: '/code-ownership'
	},

[github-actions]

Problem: Destination is another redirect
Fix: change the destination to /self-hosted/http-https-configuration

Suggested change

	{
	source: '/ownership/tls',
	destination: '/admin/tls_ssl'
	},
	{
	source: '/ownership/tls',
	destination: '/self-hosted/http-https-configuration'
	},