Zed Improved. Aiming to improve upon Zed and make a truly delightful code editor.
https://zed.dev
b28507d2e0
This PR changes how we ask users to draft up PRs and how release note generation happens. We no longer force the user to create the markdown URL link, but we do ask them to use the `closes` [GitHub magic word](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue) to link the PR to an issue, so that the issue is closed automatically when closing the PR. As for the changelog release notes, we are no longer linking to the issues, but the PR itself, which should contain the issue if a reader wants to dive further back. This makes our output more consistent, as every line will have a link, even if there is no issue associated, and it removes the need for us to try to parse the issue url in the body to try to correct mistakes in how they were forming Markdown urls - the PR url is always returned in the request, which makes it easy. **Lastly, it's just a lot less annoying to make the release notes.** The new PR format will be: ``` Closes #ISSUE Release Notes: - Added/Fixed/Improved ... ``` The new script output format will be: ``` PR Title: theme: Use a non-transparent color for the fallback `title_bar.inactive_background` Credit: ([#15709](https://github.com/zed-industries/zed/pull/15709); thanks [maxdeviant](https://github.com/maxdeviant)) Release Notes: - linux: Changed the fallback color of `title_bar.inactive_background` to a non-transparent value. -------------------------------------------------------------------------------- PR Title: Skip over folded regions when iterating over multibuffer chunks Credit: ([#15646](https://github.com/zed-industries/zed/pull/15646); thanks [osiewicz](https://github.com/osiewicz)) Release Notes: - Fixed poor performance when editing in the assistant panel after inserting large files using slash commands -------------------------------------------------------------------------------- ``` This still requires us to manually apply the credit line, but the line is already fully formed, so this should still be faster than having to manually create that line / fix any line where someone messed it up (which was all the time). I would just automatically apply it to the release notes, but sometimes we have multiple bullet points in a single PR and no real structure is enforced, so I foresee doing anything automatic breaking and needing manual adjustment. Release Notes: - N/A |
||
|---|---|---|
| .cargo | ||
| .cloudflare | ||
| .config | ||
| .github | ||
| .zed | ||
| assets | ||
| crates | ||
| docs | ||
| extensions | ||
| script | ||
| tooling/xtask | ||
| .dockerignore | ||
| .git-blame-ignore-revs | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| Cargo.lock | ||
| 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 | ||
| README.md | ||
| renovate.json | ||
| rust-toolchain.toml | ||
| shell.nix | ||
| typos.toml | ||
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
On macOS and Linux you can download Zed directly or install Zed via your local package manager.
Other platforms are not yet available:
- Windows (tracking issue)
- Web (tracking issue)
Developing Zed
- Building Zed for macOS
- Building Zed for Linux
- Building Zed for Windows
- Running Collaboration Locally
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 specifiederror for a crate you've created? If so, addpublish = falseunder[package]in your crate's Cargo.toml. - Is the error
failed to satisfy license requirementsfor 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 theacceptedarray inscript/licenses/zed-licenses.toml. - Is
cargo-aboutunable to find the license for a dependency? If so, add a clarification field at the end ofscript/licenses/zed-licenses.toml, as specified in the cargo-about book.