John D. Swanson
5d3e9c0a57
## Summary Routine housekeeping to remove seven inactive GitHub Actions workflows, surfaced by a workflow-activity review (run history via the Actions API). The removals fall into two groups: - **Four hand-written workflows** that are manually disabled, never run, or long dormant. - **Three xtask-generated workflows** (manual eval/perf tools) dormant for >90 days — removed at the source in `tooling/xtask` and regenerated, with now-unused helper code dropped. Reusable workflows `extension_tests` and `extension_bump` were intentionally **kept** — their low standalone run counts are an artifact of `workflow_call` (they run constantly via `run_tests` and `extension_auto_bump`), so they are not dormant. ## What is being removed | Workflow | Roughly what it does | Author | Last run | Reason | |---|---|---|---|---| | `assign-reviewers.yml` | Auto-assigns reviewers to PRs (via a GitHub App token) | John D. Swanson | 2026-04-17 | Manually disabled in Actions settings | | `assign_contributor_issue.yml` | Assigns/labels contributor issues and notifies Slack | Lena | 2026-05-12 | Manually disabled in Actions settings | | `background_agent_mvp.yml` | Experimental background-agent MVP (manual dispatch; schedule commented out) | morgankrey | 2026-02-24 | Dormant >90 days; experimental, never promoted | | `randomized_tests.yml` | Runs randomized tests via `script/randomized-test-ci` | Max Brunsfeld | never | Never run; only triggers on pushes to a branch that is never pushed | | `compare_perf.yml` \* | Manual perf comparison between two commits for a crate | Conrad Irwin | 2025-11-06 | Dormant >90 days; on-demand tool | | `run_unit_evals.yml` \* | Manual agent unit evals for a given model/commit | Ben Kunkle | 2025-11-14 | Dormant >90 days; on-demand tool | | `run_cron_unit_evals.yml` \* | Agent unit evals across a model matrix (manual dispatch) | Richard Feldman | 2026-01-27 | Dormant >90 days; on-demand tool | \* xtask-generated — removed via `tooling/xtask` and regenerated (commit 2). ## Notes - **Commit 1** removes the four hand-written workflows. - **Commit 2** removes the three xtask-generated workflows: it deletes their generator modules and registry entries, regenerates with `cargo xtask workflows`, and drops the helper code left unused by the removal (`vars` secrets and `steps::git_checkout`). Regeneration is a no-op for all other workflows, and `./script/clippy` (deny-warnings) is clean. Release Notes: - N/A
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 (macOS/Linux/Windows).
Other platforms are not yet available:
- Web (tracking discussion)
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
Zed source code is licensed primarily under GPL-3.0-or-later, with Apache-2.0 components where marked.
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.
Sponsorship
Zed is developed by Zed Industries, Inc., a for-profit company.
If you’d like to financially support the project, you can do so via GitHub Sponsors. Sponsorships go directly to Zed Industries and are used as general company revenue. There are no perks or entitlements associated with sponsorship.