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
Conrad Irwin 34efb23bf6 Fix a circular reference between Client and UserStore
Before this change once the UserStore had been created, the Client would
never be dropped.
2024-01-22 23:05:58 -07:00
.cargo Remove 2 suffix from gpui_macros, fix compile errors in tests 2024-01-03 13:12:21 -08:00
.config
.github Run tests even if lint/fmt/spell/squawk fails 2024-01-22 10:00:32 -07:00
.zed Use auto formatter settings for Zed repo. 2024-01-12 12:00:18 +02:00
assets Merge remote-tracking branch 'origin/main' into chat-font-size 2024-01-20 14:51:53 -07:00
crates Fix a circular reference between Client and UserStore 2024-01-22 23:05:58 -07:00
docs Store the impersonator id on access tokens created via ZED_IMPERSONATE (#4108) 2024-01-18 10:26:34 -08:00
plugins
script Introduce a ZED_MEASUREMENTS env var and use it to measure frame time 2024-01-22 11:39:20 +01:00
.dockerignore
.gitignore Rework db-seeding, so that it doesn't depend on a github auth token 2024-01-17 13:28:58 -08:00
.gitmodules
.mailmap Add Git .mailmap file (#4138) 2024-01-18 17:38:28 -05:00
Cargo.lock collab 0.40.0 2024-01-22 17:30:55 -08:00
Cargo.toml Add API for retrieving the date that a contributor signed the CLA 2024-01-22 13:11:24 -08:00
CONTRIBUTING.md Fix a few more typos 2024-01-17 14:58:58 -08:00
debug.plist
docker-compose.sql
docker-compose.yml
Dockerfile
Procfile Upload panics via zed.dev instead 2024-01-17 22:55:15 -07:00
README.md Update README.md 2024-01-17 13:24:05 -05:00
rust-toolchain.toml Remove redundant install Rust steps 2024-01-11 14:11:13 +02:00
typos.toml Remove VS Code themes (#4139) 2024-01-18 17:52:22 -05:00

🚧 TODO 🚧

  • Add intro
  • Add link to contributing guide
  • Add barebones running zed from source instructions
  • Link out to further dev docs

Zed

CI

Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.

Developing 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.