78cea18edd
This commit introduces a new workflow for managing nightly builds, allowing developers to include specific PRs in nightly releases by commenting on their pull requests. This approach provides more control over what gets included in nightly builds, enabling testing of features that aren't ready for the main branch. The workflow works by: 1. Adding a new action that listens for '/nightly' comments on PRs 2. Updating the comment with the specific commit SHA 3. Creating a 'nightly-train' branch that cherry-picks marked commits 4. Running the nightly build process on this 'nightly-train' branch This system allows for more flexible and controlled nightly releases, improving our ability to test and validate new features before they reach the main branch.
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.