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
Max Brunsfeld c6c56c35df
Downgrade LiveKit client (#4096)
There's a deadlock that we're seeing when joining a room, which we think
is a bug in the LiveKit client.

Also, we're still getting crashes when leaving calls:
https://github.com/livekit/client-sdk-swift/issues/299.

At this point, we believe both problems are due to recent changes to the
LiveKit swift sdk.
2024-01-17 11:17:22 -08:00
.cargo Remove 2 suffix from gpui_macros, fix compile errors in tests 2024-01-03 13:12:21 -08:00
.config
.github One of these days... 2024-01-11 21:22:00 -07:00
.vscode
.zed Use auto formatter settings for Zed repo. 2024-01-12 12:00:18 +02:00
assets Add CONTRIBUTING.md (#3656) 2024-01-17 13:12:14 -05:00
crates Downgrade LiveKit client (#4096) 2024-01-17 11:17:22 -08:00
docs Reorganize building zed doc 2024-01-17 13:20:27 -05:00
plugins
script Do not run squawk tests outside of PR builds 2024-01-15 16:20:53 +02:00
.dockerignore
.gitignore
.gitmodules
Cargo.lock Add the color crate (#4063) 2024-01-17 11:47:23 -05:00
Cargo.toml chore: Revert asset compression 2024-01-11 13:42:57 +01:00
CONTRIBUTING.md Refine MVP CONTRIBUTING.md 2024-01-17 12:32:08 -05:00
debug.plist
docker-compose.sql
docker-compose.yml
Dockerfile
Procfile
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

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