docs: redirect duplicate CLI command pages to canonical URLs

D-K-P · D-K-P · commit 3c3898790b34 · 2026-06-18T12:41:59.000+01:00
diff --git a/docs/cli-deploy.mdx b/docs/cli-deploy.mdx
diff --git a/docs/cli-dev.mdx b/docs/cli-dev.mdx
diff --git a/docs/cli-development-commands.mdx b/docs/cli-development-commands.mdx
diff --git a/docs/deploy-environment-variables.mdx b/docs/deploy-environment-variables.mdx
@@ -230,7 +230,7 @@ To sync environment variables from your Vercel projects to Trigger.dev, you can
 
 #### Deploy
 
-When you run the [CLI deploy command](/cli-deploy) directly or using [GitHub Actions](/github-actions) it will sync the environment variables from [Infisical](https://infisical.com) to Trigger.dev. This means they'll appear on the Environment Variables page so you can confirm that it's worked.
+When you run the [CLI deploy command](/cli-deploy-commands) directly or using [GitHub Actions](/github-actions) it will sync the environment variables from [Infisical](https://infisical.com) to Trigger.dev. This means they'll appear on the Environment Variables page so you can confirm that it's worked.
 
 This means that you need to redeploy your Trigger.dev tasks if you change the environment variables in [Infisical](https://infisical.com).
 
diff --git a/docs/deployment/overview.mdx b/docs/deployment/overview.mdx
@@ -6,7 +6,7 @@ description: "Learn how to deploy your tasks to Trigger.dev."
 
 import CorepackError from "/snippets/corepack-error.mdx";
 
-Before you can run production workloads on Trigger.dev, you need to deploy your tasks. The only way to do this at the moment is through the [deploy CLI command](/cli-deploy):
+Before you can run production workloads on Trigger.dev, you need to deploy your tasks. The only way to do this at the moment is through the [deploy CLI command](/cli-deploy-commands):
 
 <CodeGroup>
 
diff --git a/docs/docs.json b/docs/docs.json
@@ -195,7 +195,7 @@
           {
             "group": "Development",
             "pages": [
-              "cli-dev"
+              "cli-dev-commands"
             ]
           },
           {
@@ -746,6 +746,18 @@
     ]
   },
   "redirects": [
+    {
+      "source": "/cli-dev",
+      "destination": "/cli-dev-commands"
+    },
+    {
+      "source": "/cli-deploy",
+      "destination": "/cli-deploy-commands"
+    },
+    {
+      "source": "/cli-development-commands",
+      "destination": "/cli-dev-commands"
+    },
     {
       "source": "/v3/feature-matrix",
       "destination": "https://feedback.trigger.dev/roadmap"
diff --git a/docs/open-source-self-hosting.mdx b/docs/open-source-self-hosting.mdx
@@ -156,7 +156,7 @@ TRIGGER_DOMAIN=1234-42-42-42-42.ngrok-free.app
 
 ### Registry setup
 
-If you want to deploy v3 projects, you will need access to a Docker registry. The [CLI deploy](/cli-deploy) command will push the images, and then the worker machine can pull them when needed. We will use Docker Hub as an example.
+If you want to deploy v3 projects, you will need access to a Docker registry. The [CLI deploy](/cli-deploy-commands) command will push the images, and then the worker machine can pull them when needed. We will use Docker Hub as an example.
 
 1. Sign up for a free account at [Docker Hub](https://hub.docker.com/)
 
diff --git a/docs/snippets/deplopying-your-task.mdx b/docs/snippets/deplopying-your-task.mdx
@@ -1,6 +1,6 @@
 ## Deploying your task to Trigger.dev
 
-For this guide, we'll manually deploy your task by running the [CLI deploy command](/cli-deploy) below. Other ways to deploy are listed in the next section.
+For this guide, we'll manually deploy your task by running the [CLI deploy command](/cli-deploy-commands) below. Other ways to deploy are listed in the next section.
 
 <CodeGroup>
 
diff --git a/docs/snippets/useful-next-steps.mdx b/docs/snippets/useful-next-steps.mdx
@@ -7,7 +7,7 @@
    <Card title="Writing tasks" icon="pen-nib" href="/writing-tasks-introduction">
     Learn how to write your own tasks
   </Card>
-  <Card title="Deploy using the CLI" icon="terminal" href="/cli-deploy">
+  <Card title="Deploy using the CLI" icon="terminal" href="/cli-deploy-commands">
     Learn how to deploy your task manually using the CLI
   </Card>
    <Card title="Deploy using GitHub actions" icon="github" href="/github-actions">
diff --git a/docs/tasks/scheduled.mdx b/docs/tasks/scheduled.mdx
@@ -95,7 +95,7 @@ There are two ways of doing this:
 
 ### Declarative schedules
 
-These sync when you run the [dev](/cli-dev) or [deploy](/cli-deploy) commands.
+These sync when you run the [dev](/cli-dev-commands) or [deploy](/cli-deploy-commands) commands.
 
 To create them you add the `cron` property to your `schedules.task()`. This property is optional and is only used if you want to add a declarative schedule to your task:
 
@@ -127,7 +127,7 @@ export const secondScheduledTask = schedules.task({
 });
 ```
 
-When you run the [dev](/cli-dev) or [deploy](/cli-deploy) commands, declarative schedules will be synced. If you add, delete or edit the `cron` property it will be updated when you run these commands. You can view your schedules on the Schedules page in the dashboard.
+When you run the [dev](/cli-dev-commands) or [deploy](/cli-deploy-commands) commands, declarative schedules will be synced. If you add, delete or edit the `cron` property it will be updated when you run these commands. You can view your schedules on the Schedules page in the dashboard.
 
 ### Imperative schedules
 
diff --git a/docs/video-walkthrough.mdx b/docs/video-walkthrough.mdx
@@ -20,4 +20,4 @@ description: "Go from zero to a working task in your Next.js app in 10 minutes."
 - [1:44](https://youtu.be/YH_4c0K7fGM?si=J8svVzotZtyTXDap&t=104) – [Run and test](/run-tests) the "Hello, world!" example project
 - [2:09](https://youtu.be/YH_4c0K7fGM?si=FMTP8ep_cDBCU0_x&t=128) – Create and run an AI image generation task that uses [Fal.ai](https://fal.ai) – ([View the code](/guides/examples/fal-ai-image-to-cartoon))
 - [6:25](https://youtu.be/YH_4c0K7fGM?si=pPc8iLI2Y9FGD3yo&t=385) – Create and run a [Realtime](/realtime/overview) example using [React hooks](/realtime/react-hooks) – ([View the code](/guides/examples/fal-ai-realtime))
-- [11:10](https://youtu.be/YH_4c0K7fGM?si=Mjd0EvvNsNlVouvY&t=670) – [Deploy your task](/cli-deploy) to the Trigger.dev Cloud
+- [11:10](https://youtu.be/YH_4c0K7fGM?si=Mjd0EvvNsNlVouvY&t=670) – [Deploy your task](/cli-deploy-commands) to the Trigger.dev Cloud

Original file line number	Diff line number	Diff line change
`@@ -195,7 +195,7 @@`
`195`	`195`	`{`
`196`	`196`	`"group": "Development",`
`197`	`197`	`"pages": [`
`198`		`- "cli-dev"`
	`198`	`+ "cli-dev-commands"`
`199`	`199`	`]`
`200`	`200`	`},`
`201`	`201`	`{`
`@@ -746,6 +746,18 @@`
`746`	`746`	`]`
`747`	`747`	`},`
`748`	`748`	`"redirects": [`
	`749`	`+ {`
	`750`	`+ "source": "/cli-dev",`
	`751`	`+ "destination": "/cli-dev-commands"`
	`752`	`+ },`
	`753`	`+ {`
	`754`	`+ "source": "/cli-deploy",`
	`755`	`+ "destination": "/cli-deploy-commands"`
	`756`	`+ },`
	`757`	`+ {`
	`758`	`+ "source": "/cli-development-commands",`
	`759`	`+ "destination": "/cli-dev-commands"`
	`760`	`+ },`
`749`	`761`	`{`
`750`	`762`	`"source": "/v3/feature-matrix",`
`751`	`763`	`"destination": "https://feedback.trigger.dev/roadmap"`