Roshan Padaki
1eb6fb0b5d
In #17108, we updated `go test ./...` to run against the package directory, to fix cases in which the top-level project is not the go module root. However, this leads to the confusing behavior of `go test ./...` only running tests in subdirectories of the current package. Here, we change the behavior to instead walk up the dirtree to find the closest `go.mod`, and run the `./...` tasks relative to that directory. This might lead to more predictable behavior for these tasks. Also see: https://github.com/zed-industries/zed/pull/19987#issuecomment-2450159099 Release Notes: - Improved go test and generate `./...` commands to run against the current go module directory rather than the current package directory
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.