Nathan Sobo
355aebd0e4
This PR introduces a new script for iterative development of prompt overrides in Zed. Just `script/prompts link` and your running Zed should start using prompts from `zed/assets/prompts`. Use `script/prompts unlink` to undo. You can also link with `script/prompts link --worktree` to store the prompts to a `../zed_prompts` worktree that's a sibling of your repo, in case you don't want to mess with your working copy. Just don't forget about it! Key changes: - Add new `script/prompts` for managing prompt overrides - Rename `prompt_templates_dir` to `prompt_overrides_dir` for clarity - Update paths to use `~/.config/zed/prompt_overrides` instead of `~/.config/zed/prompts/templates` - Adjust `PromptBuilder` to use the new `prompt_overrides_dir` function These changes simplify the process of customizing prompts and provide a more intuitive naming convention for override-related functionality. Release Notes: - N/A
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
On macOS and Linux you can download Zed directly or install Zed via your local package manager.
Other platforms are not yet available:
- Windows (tracking issue)
- Web (tracking issue)
Developing Zed
- Building Zed for macOS
- Building Zed for Linux
- Building Zed for Windows
- Running Collaboration Locally
Contributing
See CONTRIBUTING.md for ways you can contribute to Zed.
Also... we're hiring! Check out our jobs page for open roles.
Licensing
License information for third party dependencies must be correctly provided for CI to pass.
We use cargo-about to automatically comply with open source licenses. If CI is failing, check the following:
- Is it showing a
no license specifiederror for a crate you've created? If so, addpublish = falseunder[package]in your crate's Cargo.toml. - Is the error
failed to satisfy license requirementsfor a dependency? If so, first determine what license the project has and whether this system is sufficient to comply with this license's requirements. If you're unsure, ask a lawyer. Once you've verified that this system is acceptable add the license's SPDX identifier to theacceptedarray inscript/licenses/zed-licenses.toml. - Is
cargo-aboutunable to find the license for a dependency? If so, add a clarification field at the end ofscript/licenses/zed-licenses.toml, as specified in the cargo-about book.