ᴀᴍᴛᴏᴀᴇʀ
b948d8b9e7
This PR includes several minor modifications and improvements related to Git hosting providers, covering the following areas: 1. Bitbucket Owner Parsing Fix: Remove the common `scm` prefix from the remote URL of self-hosted Bitbucket instances to prevent incorrect owner parsing. [Reference](https://github.com/gitkraken/vscode-gitlens/blob/a6e3c6fbb255116507eaabaa9940c192ed7bb0e1/src/git/remotes/bitbucket-server.ts#L72-L74) 2. Bitbucket Avatars in Blame: Add support for displaying Bitbucket avatars in the Git blame view. <img width="2750" height="1994" alt="CleanShot 2025-11-10 at 20 34 40@2x" src="https://github.com/user-attachments/assets/9e26abdf-7880-4085-b636-a1f99ebeeb97" /> 3. Self-hosted SourceHut Support: Add support for self-hosted SourceHut instances. 4. Configuration: Add recently introduced self-hosted Git providers (Gitea, Forgejo, and SourceHut) to the `git_hosting_providers` setting option. <img width="2750" height="1994" alt="CleanShot 2025-11-10 at 20 33 48@2x" src="https://github.com/user-attachments/assets/44ffc799-182d-4145-9b89-e509bbc08843" /> Closes #11043 Release Notes: - Improved self-hosted git provider support and Bitbucket integration
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
On macOS, Linux, and Windows you can download Zed directly or install Zed via your local package manager.
Other platforms are not yet available:
- 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.