zed
| Name | Last commit date |
|---|---|
| .cargo | 2 years ago |
| .config | 3 years ago |
| .github | 2 years ago |
| .zed | 2 years ago |
| assets | 2 years ago |
| crates | 2 years ago |
| docs | 2 years ago |
| plugins | 3 years ago |
| script | 2 years ago |
| .dockerignore | 3 years ago |
| .gitignore | 2 years ago |
| .gitmodules | 4 years ago |
| .mailmap | 2 years ago |
| Cargo.lock | 2 years ago |
| Cargo.toml | 2 years ago |
| CODE_OF_CONDUCT.md | 2 years ago |
| CONTRIBUTING.md | 2 years ago |
| debug.plist | 2 years ago |
| docker-compose.sql | 2 years ago |
| docker-compose.yml | 2 years ago |
| Dockerfile | 2 years ago |
| LICENSE-AGPL | 2 years ago |
| LICENSE-APACHE | 2 years ago |
| LICENSE-GPL | 2 years ago |
| Procfile | 2 years ago |
| README.md | 2 years ago |
| rust-toolchain.toml | 2 years ago |
| typos.toml | 2 years ago |
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Developing Zed
Contributing
See CONTRIBUTING.md for ways you can contribute to Zed.
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.