Code at the speed of thought – Zed is a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Find a file
2024-01-24 17:58:09 +00:00
.cargo
.config
.github Add GitHub items 2024-01-24 12:26:15 -05:00
.zed
assets Remove unused font 2024-01-24 13:14:47 +01:00
crates Replace tempdir crate with tempfile 2024-01-24 17:58:09 +00:00
docs Make it clearer that macOS Sonoma is supported (#4249) 2024-01-24 09:59:13 -05:00
plugins
script Don't error when checking target dir size if there is no target dir 2024-01-23 17:17:47 -08:00
.dockerignore
.gitignore
.gitmodules
.mailmap Add Git .mailmap file (#4138) 2024-01-18 17:38:28 -05:00
Cargo.lock Replace tempdir crate with tempfile 2024-01-24 17:58:09 +00:00
Cargo.toml Replace tempdir crate with tempfile 2024-01-24 17:58:09 +00:00
CODE_OF_CONDUCT.md Add CODE_OF_CONDUCT.md (#4239) 2024-01-23 22:31:39 -05:00
CONTRIBUTING.md Revise contributing.md 2024-01-23 11:42:40 -07:00
debug.plist
docker-compose.sql
docker-compose.yml
Dockerfile
LICENSE-AGPL chore: Add crate licenses. (#4158) 2024-01-23 16:56:22 +01:00
LICENSE-APACHE chore: Add crate licenses. (#4158) 2024-01-23 16:56:22 +01:00
LICENSE-GPL chore: Change AGPL-licensed crates to GPL (except for collab) (#4231) 2024-01-24 00:26:58 +01:00
Procfile
README.md Balance headings in README (#4238) 2024-01-23 22:15:37 -05:00
rust-toolchain.toml
typos.toml Move file finder tests to their own file 2024-01-23 15:39:51 -08:00

Zed

CI

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 specified error for a crate you've created? If so, add publish = false under [package] in your crate's Cargo.toml.
  • Is the error failed to satisfy license requirements for 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 the accepted array in script/licenses/zed-licenses.toml.
  • Is cargo-about unable to find the license for a dependency? If so, add a clarification field at the end of script/licenses/zed-licenses.toml, as specified in the cargo-about book.