fix(#1896): drop self-authored issue/pr creation wakes in forge_notify

This commit is contained in:
damocles 2026-06-24 22:19:32 +02:00
commit ca44fd56df
2 changed files with 74 additions and 7 deletions

View file

@ -141,10 +141,10 @@ silently (mark-read without delivery):
- **Self-authored comments / reviews** — comment payload's
`user.login` matches `own_login`.
Self-authored *new items* (an agent opening its own PR/issue) are not
filtered and do surface — the notification subject carries no author
field to match against without a per-notification fetch.
- **Self-authored creations** (an agent opening its own PR/issue) — the
already-fetched subject payload's poster `user.login` matches
`own_login`. Only *creations* are dropped; a later state change on the
agent's own subject is driven by someone else and still surfaces.
`own_login` is fetched once at startup via `GET /api/v1/user`. On
fetch failure the filter degrades open (no filtering) rather than