From 7b7af9191088cd16f39c79946d4cdd479046e51d Mon Sep 17 00:00:00 2001 From: Johannes Date: Wed, 1 Jul 2026 16:24:06 -0400 Subject: [PATCH] =?UTF-8?q?content(guide):=20note=20issue-close=20auto-not?= =?UTF-8?q?ifies=20reporter=20=E2=80=94=20fill=20Resolution=20first=20(pro?= =?UTF-8?q?cesses.gitea-issues)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Ties in dlx-claude's gitea-notify webhook: closing a Gitea issue DMs the reporter in their HiveIQ inbox using the Resolution field. Co-Authored-By: Claude Opus 4.8 --- .../resources/content/processes/gitea-issues/overview.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/backend/src/main/resources/content/processes/gitea-issues/overview.md b/backend/src/main/resources/content/processes/gitea-issues/overview.md index 0e83d71..3659962 100644 --- a/backend/src/main/resources/content/processes/gitea-issues/overview.md +++ b/backend/src/main/resources/content/processes/gitea-issues/overview.md @@ -27,10 +27,16 @@ already exist (avoid duplicates). - **Frontend** fixes → **tristan** (QA). **Backend** fixes → **johannes** (tristan can't test backend). - `erin` has no Gitea account yet — assign only `tristan` until she does. -## Closing — always manual +## Closing — always manual (and it now notifies the reporter) **Never close an issue via the API.** Claude applies labels and comments only. The team closes issues in the Gitea UI after verification. Never PATCH `state: closed`. +> **Closing an issue auto-notifies the reporter.** A Gitea webhook (`gitea-notify`, built by +> dlx-claude 2026-07-01) sends the reporter a DIRECT message in their HiveIQ inbox when an issue is +> closed — using the **Resolution** field from the issue template. **Fill in the Resolution before +> closing** so the customer gets a meaningful message. (Reporter email is read from the issue body; +> if they're not a HiveIQ user, the notification is silently skipped.) + ## A fix isn't done until its issue is reconciled After deploying a fix: **comment the fix on the matching issue + apply `Verify Fix` + assign the verifier.** Never leave a deployed fix with a stale/untouched issue.