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
Marshall Bowers f3a76c8636
Remove VS Code themes (#4139)
This PR removes the VS Code themes from the `assets/` directory, as
we're not currently using them (and it's unlikely we will in their
current state).

Release Notes:

- N/A
2024-01-18 17:52:22 -05:00
.cargo
.config
.github Adjust config 2024-01-17 17:07:04 -08:00
.vscode
.zed
assets Remove VS Code themes (#4139) 2024-01-18 17:52:22 -05:00
crates gpui: Always recompute layout on cache miss. (#4131) 2024-01-18 14:44:35 -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 Restore the colored background for collaborators that you are following (#4137) 2024-01-18 14:32:54 -08:00
.dockerignore
.gitignore
.gitmodules
.mailmap Add Git .mailmap file (#4138) 2024-01-18 17:38:28 -05:00
Cargo.lock collab 0.37.0 2024-01-18 10:29:05 -08:00
Cargo.toml
CONTRIBUTING.md
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
rust-toolchain.toml
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.