Files
zed/assets/settings/initial_worktree_setup_tasks.json
yenru0 fe62a99bf5 gwen: Purge remaining Zed branding from user-facing surfaces
Sweep every user-visible product string to Gwen: app menus (Quit,
Hide, Gwen Repository), feedback links (repo/issues now point at
github.com/kk376/zed, email to yenru@yrkaierx.com), move-to-Applications
and update dialogs, provider and settings copy, CLI help, installer and
desktop/flatpak/snap/plist metadata.

Rename user-facing settings values with back-compat aliases: base_keymap
"Gwen" (accepts "Zed"), fonts ".GwenMono"/".GwenSans" (accept
".ZedMono"/".ZedSans"), icon theme "Gwen (Default)". Fix F10
app-menu keymap arguments to "Gwen" and align the Windows installer
AppMutex with release_channel::app_identifier(). Internal identifiers,
wire protocol names, upstream service URLs and legal attribution are
intentionally kept.
2026-09-29 09:24:34 +09:00

24 lines
1.0 KiB
JSON

// Worktree setup tasks, stored in this project's tasks.json.
// See https://zed.dev/docs/tasks#hooks for the full Tasks Hooks documentation.
//
// Tasks with the `create_worktree` hook run automatically right after Gwen
// creates a new git worktree. Use them to get a fresh worktree ready to work
// in — for example, installing dependencies or copying files that git doesn't
// track (like `.env`) from the original repository.
//
// Two variables are available to these tasks:
// * $ZED_WORKTREE_ROOT — the root directory of the newly created worktree
// * $ZED_MAIN_GIT_WORKTREE — the original repository's working directory
//
// Uncomment the example below and adjust the command to get started.
// Note: hooked tasks run as soon as a worktree is created, so only enable
// commands you want to run automatically.
[
// {
// "label": "Set up new worktree",
// "command": "cp -n \"$ZED_MAIN_GIT_WORKTREE/.env\" \"$ZED_WORKTREE_ROOT/\" && npm install",
// "cwd": "$ZED_WORKTREE_ROOT",
// "hooks": ["create_worktree"]
// }
]