Ryan HawkinsandMarshall Bowers
a4baba7edd
The git blame dialog doesn't give the user a way to quickly copy the SHA of the associated commit for a line. Adding an option for users to quickly access this SHA is helpful for user's to do any more git-fu they might need, such as viewing the full changes themselves within git, checking the commit out, bisecting off the commit, etc. This is also very handy for user's of self-hosted git providers. Determining what provider a self-hosted repository is using could be quite difficult and this presents an easy option to allow users to look up more about a commit without having to memorize the short SHA. Release Notes: - Added a button to copy the SHA from a Git blame entry. <img width="1552" alt="A screenshot showing the new copy SHA button within the Zed editor's inline blame " src="https://github.com/user-attachments/assets/9365950d-3a3f-4c11-b119-ab02654f5669"> --------- Co-authored-by: Marshall Bowers <elliott.codes@gmail.com>
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.