Richard Feldman
a30bc615e2
When archiving a thread's linked worktree, `git worktree remove` can fail to delete the working directory while still removing the admin metadata in `.git/worktrees/<name>`. This leaves an orphaned folder on disk that no longer appears in `git worktree list`. ## Fix Delete the directory ourselves first with `std::fs::remove_dir_all`, then call `git worktree remove --force` to clean up only the admin entry. Git already handles the case where the working tree is already gone (since [git/git@ee6763a](https://github.com/git/git/commit/ee6763af0a3b97225803c6c908a29de40336cf38)). Also fixes `FakeGitRepository::remove_worktree` to handle a missing working tree directory (matching real git behavior) by scanning `.git/worktrees/` entries when the `.git` pointer file can't be read. Release Notes: - Fixed archiving an agent thread sometimes leaving the worktree folder on disk even though the git worktree was removed.
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.