From af75a7010e1bd08a2364d9fdb17a37b6374d803b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?R=C5=ABdolfs=20O=C5=A1i=C5=86=C5=A1?= Date: Tue, 13 Oct 2026 12:24:41 +0200 Subject: [PATCH] Ask for component labels on patches With explorer, desktop and httpd in one repo, the labels show at a glance which projects a patch touches. --- CLAUDE.md | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/CLAUDE.md b/CLAUDE.md index a0b1e0ff9..b97667ff4 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -59,6 +59,26 @@ checks and conventions: - Capitalize subject, no trailing period, max 50 chars - Prefix backend-only commits with `httpd:` +### Patches + +Label every new patch with each component it touches, so reviewers and +filters can tell the projects apart: + +| Label | Covers | +|---|---| +| `explorer` | the web app at the root: `src/`, `http-client/`, `workers/`, its tests and config | +| `desktop` | anything under `desktop/` | +| `httpd` | `crates/radicle-httpd/` and `crates/radicle-search/` | + +A patch that touches several components gets several labels. Changes to +shared files (`.github/`, `.buildkite/`, `.ryph/`, root docs) get the labels +of the components they affect. `git push` can't set labels, so add them +once the patch is open: + +```sh +rad patch label --add explorer --add httpd +``` + ### Releases and tags Each project is released on its own. Release tags are