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-18 13:47:43 -08:00
.cargo
.config
.github Adjust config 2024-01-17 17:07:04 -08:00
.vscode
.zed Use auto formatter settings for Zed repo. 2024-01-12 12:00:18 +02:00
assets Revert vscode theme changes 2024-01-17 15:56:15 -08:00
crates Restore the colored background for collaborators that you're following 2024-01-18 13:47:43 -08:00
docs Store the impersonator id on access tokens created via ZED_IMPERSONATE (#4108) 2024-01-18 10:26:34 -08:00
plugins
script Account for titlebar when tiling windows in zed-local 2024-01-18 13:42:11 -08: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
Cargo.lock collab 0.37.0 2024-01-18 10:29:05 -08:00
Cargo.toml chore: Revert asset compression 2024-01-11 13:42:57 +01: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 Update procfile and local development docs, zed.dev is no longer needed 2024-01-17 13:28:58 -08: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 Adjust config 2024-01-17 17:07:04 -08: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.