fix: update links for dev docs (#62758)

* fix: license checker info is in docs-legacy

* fix: update remaining dev links

Author: bahrmichael

.github/workflows/licenses-update.yml

@@ -39,7 +39,7 @@ jobs:
         team-reviewers: 'team-dev-infra'
         body: |
           This is an automated pull request generated by [this run](https://github.com/sourcegraph/sourcegraph/actions/runs/${{ github.run_id }}).
-          Learn more about our GitHub Actions for managing licenses [here](https://docs.sourcegraph.com/dev/background-information/ci#third-party-licenses).
+          Learn more about our GitHub Actions for managing licenses [here](https://docs-legacy.sourcegraph.com/dev/background-information/ci#third-party-licenses).
 
           You're safe to merge this pull request when the required checks are passing.
 

CONTRIBUTING.md

@@ -19,10 +19,10 @@ All interactions with the Sourcegraph open source project are governed by the
 
 1. Select one of the issues labeled as [good first issue](https://github.com/orgs/sourcegraph/projects/210).
 2. Clone the repo: `git clone https://github.com/sourcegraph/sourcegraph`.
-3. [Set up your development environment](https://sourcegraph.com/docs/dev/setup/quickstart) to run the project locally.
-4. Before creating a pull request, ensure that [recommended checks](https://sourcegraph.com/docs/dev/contributing) pass locally. We're actively working on making our CI pipeline public to automate this step.
+3. [Set up your development environment](https://docs-legacy.sourcegraph.com/dev/setup/quickstart) to run the project locally.
+4. Before creating a pull request, ensure that [recommended checks](https://docs-legacy.sourcegraph.com/dev/contributing) pass locally. We're actively working on making our CI pipeline public to automate this step.
 5. **IMPORTANT:** Once you have a pull request ready to review, the 'verification/cla-signed' check will be flagged, and you will be prompted to sign the CLA with a link provided by our bot. Once you sign, add a comment tagging `@sourcegraph/contribution-reviewers`. After that your pull request will be ready for review.
-   - For Sourcegraph team members, see [these notes](https://sourcegraph.com/docs/dev/contributing/accepting_contribution#cla-bot) for how to verify that the CLA has been signed.
+   - For Sourcegraph team members, see [these notes](https://docs-legacy.sourcegraph.com/dev/contributing/accepting_contribution#cla-bot) for how to verify that the CLA has been signed.
 6. Once you've chosen an issue, **comment on it to announce that you will be working on it**, making it visible for others that this issue is being tackled. If you end up not creating a pull request for this issue, please delete your comment.
 7. If you have any questions, please [refer to the docs first](https://sourcegraph.com/docs/). If you don’t find any relevant information, mention the issue author.
 8. The issue author will try to provide guidance. Sourcegraph always works in async mode. We will try to answer as soon as possible, but please keep time zones differences in mind.
@@ -37,17 +37,17 @@ All open issues are not yet solved. If the task is interesting to you, take it a
 ### Getting applications up and running
 
 - [Getting Started Guide](https://sourcegraph.com/docs/getting-started)
-- [Troubleshooting section](https://sourcegraph.com/docs/dev/setup/troubleshooting)
+- [Troubleshooting section](https://docs-legacy.sourcegraph.com/dev/setup/troubleshooting)
 
 ### How to write tests
 
-- [How to write tests](https://sourcegraph.com/docs/dev/how-to/testing)
-- [Testing principles](https://sourcegraph.com/docs/dev/background-information/testing_principles)
-- [Testing web code](https://sourcegraph.com/docs/dev/background-information/testing_web_code)
+- [How to write tests](https://docs-legacy.sourcegraph.com/dev/how-to/testing)
+- [Testing principles](https://docs-legacy.sourcegraph.com/dev/background-information/testing_principles)
+- [Testing web code](https://docs-legacy.sourcegraph.com/dev/background-information/testing_web_code)
 
 ### Pull Requests
 
-- [How to structure](https://sourcegraph.com/docs/dev/background-information/pull_request_reviews#what-makes-an-effective-pull-request-pr)
+- [How to structure](https://docs-legacy.sourcegraph.com/dev/background-information/pull_request_reviews#what-makes-an-effective-pull-request-pr)
 - Git branch name convention: `[developer-initials]/short-feature-description`
 - [Examples on Github](https://github.com/sourcegraph/sourcegraph/pulls?q=is%3Apr+label%3Ateam%2Ffrontend-platform)
-- (For Sourcegraph team) [How to accept contributions](https://sourcegraph.com/docs/dev/contributing/accepting_contribution)
+- (For Sourcegraph team) [How to accept contributions](https://docs-legacy.sourcegraph.com/dev/contributing/accepting_contribution)

client/browser/README.md

@@ -135,7 +135,7 @@ The test suite in `end-to-end/github.test.ts` runs on the release branch `bext/r
 
 The test suite in end-to-end/phabricator.test.ts tests the Phabricator native integration.
 It assumes an existing Sourcegraph and Phabricator instance that has the Phabricator extension installed.
-There are automated scripts to set up the Phabricator instance, see https://sourcegraph.com/docs/dev/phabricator_gitolite.
+There are automated scripts to set up the Phabricator instance, see https://docs-legacy.sourcegraph.com/dev/phabricator_gitolite.
 It currently does not run in CI and is intended to be run manually for release testing.
 
 `end-to-end/bitbucket.test.ts` tests the browser extension on a Bitbucket Server instance.
@@ -243,7 +243,7 @@ This is an adjusted version of @lguychard's [comment here](https://github.com/so
 4. Navigated to `127.0.0.1` to access the Phabricator instance, and logged in with `admin` / `sourcegraph` (as printed by `./dev/phabricator/start.sh`)
 5. Navigated to `http://127.0.0.1/config/group/sourcegraph/` (Config -> Application Settings -> Sourcegraph)
 6. Edited `corsOrigin` in site config at `https://sourcegraph.test:3443/site-admin/configuration` to include `http://127.0.0.1` (might need to be added in `dev-private` repo).
-7. Added a repository by mirroring a public GitHub repository (we have some docs for this [here](https://sourcegraph.com/docs/dev/phabricator_gitolite), but they need improving):
+7. Added a repository by mirroring a public GitHub repository (we have some docs for this [here](https://docs-legacy.sourcegraph.com/dev/phabricator_gitolite), but they need improving):
    - Navigated to `http://127.0.0.1/diffusion/edit/?vcs=git`
    - Created a repository with name `JsonRPC2`, callsign `JRPC`, short name `jrpc`
    - Navigated to `http://127.0.0.1/source/jrpc/manage/uris/` (URIs)

client/browser/src/end-to-end/phabricator.test.ts

@@ -97,7 +97,7 @@ async function configureSourcegraphIntegration(driver: Driver): Promise<void> {
         await driver.page.waitForSelector('a[href="/config/group/sourcegraph/"]', { timeout: 2000 })
     } catch {
         throw new Error(
-            `The Sourcegraph native integration is not installed on ${PHABRICATOR_BASE_URL}. Please see https://sourcegraph.com/docs/dev/how-to/configure_phabricator_gitolite#install-the-sourcegraph-phabricator-extension`
+            `The Sourcegraph native integration is not installed on ${PHABRICATOR_BASE_URL}. Please see https://docs-legacy.sourcegraph.com/dev/how-to/configure_phabricator_gitolite#install-the-sourcegraph-phabricator-extension`
         )
     }
 

client/shared/src/platform/context.ts

@@ -97,7 +97,7 @@ export interface PlatformContext {
      * Returns promise that resolves into Apollo Client instance after cache restoration.
      * Only `watchQuery` is available till https://github.com/sourcegraph/sourcegraph/issues/24953 is implemented.
      *
-     * @deprecated Use [Apollo](https://sourcegraph.com/docs/dev/background-information/web/graphql#graphql-client) instead
+     * @deprecated Use [Apollo](https://docs-legacy.sourcegraph.com/dev/background-information/web/graphql#graphql-client) instead
      */
     getGraphQLClient: () => Promise<Pick<GraphQLClient, 'watchQuery'>>
 
@@ -108,7 +108,7 @@ export interface PlatformContext {
      * could leak private information such as repository names.
      * @returns Observable that emits the result or an error if the HTTP request failed
      *
-     * @deprecated Use [Apollo](https://sourcegraph.com/docs/dev/background-information/web/graphql#graphql-client) instead
+     * @deprecated Use [Apollo](https://docs-legacy.sourcegraph.com/dev/background-information/web/graphql#graphql-client) instead
      */
     requestGraphQL: <R, V extends { [key: string]: any } = object>(options: {
         /**
@@ -189,7 +189,7 @@ export interface PlatformContext {
     /**
      * Telemetry recorder for the new telemetry framework, superseding
      * 'telemetryService' and 'logEvent' variants. Learn more here:
-     * https://sourcegraph.com/docs/dev/background-information/telemetry
+     * https://docs-legacy.sourcegraph.com/dev/background-information/telemetry
      *
      * It is backed by a '@sourcegraph/telemetry' implementation.
      */

client/shared/src/telemetry/event-names.ts

@@ -1,4 +1,4 @@
-// NOTE(naman): Remember to add events to allow list: https://sourcegraph.com/docs/dev/background-information/data-usage-pipeline#allow-list
+// NOTE(naman): Remember to add events to allow list: https://docs-legacy.sourcegraph.com/dev/background-information/data-usage-pipeline#allow-list
 export const enum EventName {
     CODY_CHAT_PAGE_VIEWED = 'web:codyChat:pageViewed',
     CODY_CHAT_SUBMIT = 'web:codyChat:submit',

client/shared/src/telemetry/index.ts

@@ -29,14 +29,14 @@ export type BillingProduct = 'exampleBillingProduct'
 
 /**
  * Props interface that can be extended by React components depending on the
- * new telemetry framework: https://sourcegraph.com/docs/dev/background-information/telemetry
+ * new telemetry framework: https://docs-legacy.sourcegraph.com/dev/background-information/telemetry
  * These properties are part of {@link PlatformContext}.
  */
 export interface TelemetryV2Props {
     /**
      * Telemetry recorder for the new telemetry framework, superseding
      * 'telemetryService' and 'logEvent' variants. Learn more here:
-     * https://sourcegraph.com/docs/dev/background-information/telemetry
+     * https://docs-legacy.sourcegraph.com/dev/background-information/telemetry
      *
      * It is backed by a '@sourcegraph/telemetry' implementation.
      */

client/shared/src/testing/accessibility.ts

@@ -25,7 +25,7 @@ const formatRuleViolations = (violations: Result[]): string[] =>
         ({ id, help, helpUrl, nodes }) => `
 Rule: "${id}" (${help})
 Further information: ${helpUrl}
-How to manually audit: https://sourcegraph.com/docs/dev/background-information/web/accessibility/how-to-audit#auditing-a-user-journey
+How to manually audit: https://docs-legacy.sourcegraph.com/dev/background-information/web/accessibility/how-to-audit#auditing-a-user-journey
 Required changes: ${formatViolationProblems(nodes)}
 `
     )
@@ -45,7 +45,7 @@ export const ACCESSIBILITY_AUDIT_IGNORE_CLASS = '.a11y-ignore'
  *
  * Will error with a list of violations if any are found.
  *
- * See further documentation: https://sourcegraph.com/docs/dev/how-to/testing#accessibility-tests
+ * See further documentation: https://docs-legacy.sourcegraph.com/dev/how-to/testing#accessibility-tests
  */
 export async function accessibilityAudit(page: Page, config: AccessibilityAuditConfiguration = {}): Promise<void> {
     const { options, mode = 'fail' } = config

client/shared/src/testing/integration/README.md

@@ -2,4 +2,4 @@
 
 This folder contains shared testing helpers for the Sourcegraph webapp and browser extensions.
 
-For more information about integration tests and how to run them, read the [Client integration tests documentation](https://sourcegraph.com/docs/dev/how-to/testing#client-integration-tests).
+For more information about integration tests and how to run them, read the [Client integration tests documentation](https://docs-legacy.sourcegraph.com/dev/how-to/testing#client-integration-tests).

client/storybook/README.md

@@ -1,6 +1,6 @@
 # Storybook configuration
 
-Check out the [Storybook section](https://sourcegraph.com/docs/dev/background-information/web/web_app#storybook) in the [Developing the Sourcegraph web app](https://docs.sourcegraph.com/dev/background-information/web/web_app) docs.
+Check out the [Storybook section](https://docs-legacy.sourcegraph.com/dev/background-information/web/web_app#storybook) in the [Developing the Sourcegraph web app](https://docs.sourcegraph.com/dev/background-information/web/web_app) docs.
 
 ## Usage
 

client/web/README.md

@@ -2,7 +2,7 @@
 
 ## Local development
 
-Use `sg` CLI tool to configure and start local development server. For more information check out [the `sg` documentation](https://sourcegraph.com/docs/dev/background-information/sg).
+Use `sg` CLI tool to configure and start local development server. For more information check out [the `sg` documentation](https://docs-legacy.sourcegraph.com/dev/background-information/sg).
 
 Our local development server runs by starting both a [Caddy](https://caddyserver.com/) HTTPS server and a Node HTTP server. We then can reverse proxy requests to the Node server to serve client assets under HTTPS.
 

client/web/src/components/Breadcrumbs.tsx

@@ -77,7 +77,7 @@ export interface BreadcrumbSetters {
      * pass an arbitrary element or a link config object for simpler breadcrumbs.
      * @returns Another breadcrumb setters object to pass down to child components to register child breadcrumbs,
      * with a method to remove the breadcrumb again. The object should be added to a [subscription
-     * bag](https://sourcegraph.com/docs/dev/background-information/languages/typescript#subscription-bag).
+     * bag](https://docs-legacy.sourcegraph.com/dev/background-information/languages/typescript#subscription-bag).
      */
     setBreadcrumb: (breadcrumb: NullableBreadcrumb) => BreadcrumbSetters & Unsubscribable
 }

client/web/src/telemetry/apolloTelemetryExporter.ts

@@ -6,7 +6,7 @@ import type { ExportTelemetryEventsResult } from '../graphql-operations'
 
 /**
  * ApolloTelemetryExporter exports events via the new Sourcegraph telemetry
- * framework: https://sourcegraph.com/docs/dev/background-information/telemetry
+ * framework: https://docs-legacy.sourcegraph.com/dev/background-information/telemetry
  */
 export class ApolloTelemetryExporter implements TelemetryExporter {
     constructor(private client: ApolloClient<object>) {}

client/web/src/util/constants.ts

@@ -1,6 +1,6 @@
 import type { AuthProvider } from '../jscontext'
 
-// NOTE(naman): Remember to add events to allow list: https://sourcegraph.com/docs/dev/background-information/data-usage-pipeline#allow-list
+// NOTE(naman): Remember to add events to allow list: https://docs-legacy.sourcegraph.com/dev/background-information/data-usage-pipeline#allow-list
 export const enum EventName {
     CODY_CHAT_PAGE_VIEWED = 'web:codyChat:pageViewed',
     CODY_CHAT_SUBMIT = 'web:codyChat:submit',

client/wildcard/README.md

@@ -12,4 +12,4 @@ The Wildcard component library is a collection of design-approved reusable compo
   - `hooks/`
     Reusable React hooks. Typically utilities or headless components
 
-See [Wildcard documentation](https://sourcegraph.com/docs/dev/background-information/web/wildcard) for more information.
+See [Wildcard documentation](https://docs-legacy.sourcegraph.com/dev/background-information/web/wildcard) for more information.

client/wildcard/src/components/Typography/Typography.story.tsx

@@ -267,7 +267,7 @@ export const CrossingStyles: StoryFn = () => (
             <Link
                 target="_blank"
                 rel="noopener noreferrer"
-                to="https://sourcegraph.com/docs/dev/background-information/web/accessibility/detailed-checklist#headings"
+                to="https://docs-legacy.sourcegraph.com/dev/background-information/web/accessibility/detailed-checklist#headings"
             >
                 accessible
             </Link>{' '}

cmd/gitserver/README.md

@@ -47,7 +47,7 @@ To use `p4-fusion` while developing Sourcegraph, there are a couple of options.
 
 #### Docker
 
-[Run `gitserver` in a Docker container](https://sourcegraph.com/docs/dev/background-information/sg#run-gitserver-in-a-docker-container). This is the option that gives an experience closest to a deployed Sourcegraph instance, and will work for any platform/OS on which you're developing (running `sg start`).
+[Run `gitserver` in a Docker container](https://docs-legacy.sourcegraph.com/dev/background-information/sg#run-gitserver-in-a-docker-container). This is the option that gives an experience closest to a deployed Sourcegraph instance, and will work for any platform/OS on which you're developing (running `sg start`).
 
 #### Bazel
 

cmd/gitserver/internal/cleanup.go

@@ -134,7 +134,7 @@ const (
 )
 
 // gitGCMode describes which mode we should be running git gc.
-// See for a detailed description of the modes: https://sourcegraph.com/docs/dev/background-information/git_gc
+// See for a detailed description of the modes: https://docs-legacy.sourcegraph.com/dev/background-information/git_gc
 var gitGCMode = func() int {
 	// EnableGCAuto is a temporary flag that allows us to control whether or not
 	// `git gc --auto` is invoked during janitorial activities. This flag will

cmd/telemetry-gateway/README.md

@@ -2,4 +2,4 @@
 
 Telemetry Gateway is a managed service that ingests events exported from Sourcegraph instances, manipulates them as needed, and exports them to designated Pub/Sub topics or other destinations for processing.
 
-Refer to [the Telemetry Gateway development documentation](https://sourcegraph.com/docs/dev/how-to/telemetry_gateway) for more development guidance.
+Refer to [the Telemetry Gateway development documentation](https://docs-legacy.sourcegraph.com/dev/how-to/telemetry_gateway) for more development guidance.

cmd/worker/internal/permissions/bitbucket_projects.go

@@ -371,7 +371,7 @@ func newBitbucketProjectPermissionsWorker(ctx context.Context, observationCtx *o
 }
 
 // newBitbucketProjectPermissionsResetter implements resetter for the explicit_permissions_bitbucket_projects_jobs table.
-// See resetter documentation for more details. https://sourcegraph.com/docs/dev/background-information/workers#dequeueing-and-resetting-jobs
+// See resetter documentation for more details. https://docs-legacy.sourcegraph.com/dev/background-information/workers#dequeueing-and-resetting-jobs
 func newBitbucketProjectPermissionsResetter(observationCtx *observation.Context, db database.DB, cfg *config, metrics bitbucketProjectPermissionsMetrics) *dbworker.Resetter[*types.BitbucketProjectPermissionJob] {
 	observationCtx = observation.ContextWithLogger(observationCtx.Logger.Scoped("BitbucketProjectPermissionsResetter"), observationCtx)
 

dev/build-tracker/notify/slack.go

@@ -312,9 +312,9 @@ func (c *Client) createMessageBlocks(info *BuildNotification, author string) []s
 			&slack.TextBlockObject{
 				Type: slack.MarkdownType,
 				Text: `:books: *More information on flakes*
-• <https://sourcegraph.com/docs/dev/background-information/ci#flakes|How to disable flaky tests>
+• <https://docs-legacy.sourcegraph.com/dev/background-information/ci#flakes|How to disable flaky tests>
 • <https://github.com/sourcegraph/sourcegraph/issues/new/choose|Create a flaky test issue>
-• <https://sourcegraph.com/docs/dev/how-to/testing#assessing-flaky-client-steps|Recognizing flaky client steps and how to fix them>
+• <https://docs-legacy.sourcegraph.com/dev/how-to/testing#assessing-flaky-client-steps|Recognizing flaky client steps and how to fix them>
 
 _Disable flakes on sight and save your fellow teammate some time!_`,
 			},

dev/ci/README.md

@@ -1,4 +1,4 @@
 # Buildkite Pipeline for sourcegraph/sourcegraph
 
 We dynamically generate our CI pipeline for [Buildkite](https://buildkite.com/sourcegraph/sourcegraph) based on the output of [gen-pipeline.go](./gen-pipeline.go).
-To learn more, refer to the [continuous integration docs](https://sourcegraph.com/docs/dev/background-information/ci).
+To learn more, refer to the [continuous integration docs](https://docs-legacy.sourcegraph.com/dev/background-information/ci).

dev/ci/bazel-prechecks.sh

@@ -56,7 +56,7 @@ if [[ $EXIT_CODE -ne 0 ]]; then
   sg bazel configure
   ```
 
-  #### For more information please see the [Bazel FAQ](https://sourcegraph.com/docs/dev/background-information/bazel/faq)
+  #### For more information please see the [Bazel FAQ](https://docs-legacy.sourcegraph.com/dev/background-information/bazel/faq)
 
 END
   exit "$EXIT_CODE"
@@ -80,7 +80,7 @@ if [[ $EXIT_CODE -ne 0 ]]; then
   sg bazel configure godeps
   ```
 
-  #### For more information please see the [Bazel FAQ](https://sourcegraph.com/docs/dev/background-information/bazel/faq)
+  #### For more information please see the [Bazel FAQ](https://docs-legacy.sourcegraph.com/dev/background-information/bazel/faq)
 
 END
   exit "$EXIT_CODE"