From bf0c32fc595f26d163994c202a81f4e6569bf7ec Mon Sep 17 00:00:00 2001 From: Claude Date: Wed, 4 Nov 2026 12:26:16 +0000 Subject: [PATCH] AGENTS: merge your PR when the work is finished The owner's standing instruction (2026-11-04), also in the Gabriel Design System's AGENTS.md. Claude-Session: https://claude.ai/code/session_01AFTKgVttu8z9Wu34dcvEYY --- AGENTS.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/AGENTS.md b/AGENTS.md index f5b59261..96620c64 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -3,6 +3,14 @@ Read this before touching ring/BLE hardware code (`app/src/main/java/com/pulseloop/ring/`, `app/src/main/java/com/pulseloop/wearables/`). Full detail: `docs/qring-ble-adoption.md`. +## Merge your PR when the work is finished + +**The owner's standing instruction (2026-11-04): open a PR for every change and, once it's verified +(CI green, the repo's own tests and checks run, no unresolved review threads), merge it yourself; +don't leave it waiting.** Use a merge commit, the way `main`'s history does. A release is a separate +step: the Release workflow (`release.yml`, `workflow_dispatch`) with the next `v{name}+{code}` tag, +run when the owner asks for one. The same rule is in the Gabriel Design System's AGENTS.md. + ## Commits carry no agent attribution **Do not add a `Co-Authored-By` trailer to commits in this repo** — not for Claude, not for any