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 47628515e1
assistant: Put /docs and /project behind a setting (#16186)
This PR puts the availability of the `/docs` and `/project` slash
commands behind their respective settings.

Release Notes:

- N/A
2024-08-13 17:32:24 -04:00
.cargo
.cloudflare
.config
.github
.zed
assets assistant: Put /docs and /project behind a setting (#16186) 2024-08-13 17:32:24 -04:00
crates assistant: Put /docs and /project behind a setting (#16186) 2024-08-13 17:32:24 -04:00
docs Update key-bindings.md (#15994) 2024-08-13 14:40:27 +03:00
extensions Allow extensions to suggest packages for /docs completions (#16185) 2024-08-13 16:50:57 -04:00
script Configure squawk rules (#16144) 2024-08-12 22:11:36 -04:00
tooling/xtask
.dockerignore
.git-blame-ignore-revs
.gitattributes
.gitignore
.mailmap
Cargo.lock assistant: Populate /docs rustdoc with workspace crates (#16172) 2024-08-13 14:31:34 -04:00
Cargo.toml
CODE_OF_CONDUCT.md
compose.yml
CONTRIBUTING.md
debug.plist
docker-compose.sql
Dockerfile
flake.lock
flake.nix
LICENSE-AGPL
LICENSE-APACHE
LICENSE-GPL
livekit.yaml
Procfile
Procfile.postgrest
README.md
renovate.json
rust-toolchain.toml
shell.nix
typos.toml Promote package suggestions to a first-class concept on IndexedDocsProviders (#16177) 2024-08-13 16:01:58 -04:00

Zed

CI

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


Installation

Packaging status

On macOS and Linux you can download Zed directly or install Zed via your local package manager.

Other platforms are not yet available:

Developing Zed

Contributing

See CONTRIBUTING.md for ways you can contribute to Zed.

Also... we're hiring! Check out our jobs page for open roles.

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.