From a03fb3791e0f8abfdae92a99538318786efe9814 Mon Sep 17 00:00:00 2001 From: Andy Waite Date: Fri, 11 Apr 2025 11:31:58 -0400 Subject: [PATCH] docs: Fix name for `zed: open project tasks` command (#28578) There's no `zed: open local tasks`, perhaps it was called that previously. Release Notes: - N/A --- docs/src/tasks.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/tasks.md b/docs/src/tasks.md index 7eb6fd7f8d86c2ba52b9e8495c6e2487641e787a..557bedb118927434156c6c864c2fa34467f1d4e4 100644 --- a/docs/src/tasks.md +++ b/docs/src/tasks.md @@ -65,7 +65,7 @@ Keep `"use_new_terminal": false` and set `"allow_concurrent_runs": true` to allo Tasks can be defined: - in the global `tasks.json` file; such tasks are available in all Zed projects you work on. This file is usually located in `~/.config/zed/tasks.json`. You can edit them by using the `zed: open tasks` action. -- in the worktree-specific (local) `.zed/tasks.json` file; such tasks are available only when working on a project with that worktree included. You can edit worktree-specific tasks by using the `zed: open local tasks` action. +- in the worktree-specific (local) `.zed/tasks.json` file; such tasks are available only when working on a project with that worktree included. You can edit worktree-specific tasks by using the `zed: open project tasks` action. - on the fly with [oneshot tasks](#oneshot-tasks). These tasks are project-specific and do not persist across sessions. - by language extension.