Richard Feldman
3b1d16fdee
When archiving a thread that lives on a main worktree (not a linked worktree), `build_root_plan` was still returning a `RootPlan`, which caused the archive flow to call `git worktree remove` on the main working tree. Git rightfully refuses this with: ``` fatal: '/Users/rtfeldman/code/zed' is a main working tree ``` This fix makes `build_root_plan` return `None` for non-linked worktrees, so the archive-to-disk machinery is simply skipped. The thread is marked archived in the metadata store and can be unarchived later — no git operations needed. Since `build_root_plan` now guarantees a linked worktree when it returns `Some`, `RootPlan::worktree_repo` is tightened from `Option<Entity<Repository>>` to `Entity<Repository>`, removing the fallback codepath and the `is_some()` guard in `archive_worktree_roots`. Release Notes: - Fixed a crash when archiving an agent thread that was opened on the main project (not a linked git worktree).
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
On macOS, Linux, and Windows you can download Zed directly or install Zed via your local package manager (macOS/Linux/Windows).
Other platforms are not yet available:
- Web (tracking issue)
Developing Zed
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.
Sponsorship
Zed is developed by Zed Industries, Inc., a for-profit company.
If you’d like to financially support the project, you can do so via GitHub Sponsors. Sponsorships go directly to Zed Industries and are used as general company revenue. There are no perks or entitlements associated with sponsorship.