From da2652f1dd2f692e88b2e973bb8348a2461c5955 Mon Sep 17 00:00:00 2001
From: Andrey Antukh <niwi@niwi.nz>
Date: Fri, 9 Oct 2026 17:14:05 +0000
Subject: [PATCH] :books: Note GitHub assignee limits in the issues workflow

`gh issue edit --add-assignee` fails with a 422 for users without
write permission on the repo, for non-members, and for people who
never commented, and the command still exits 0. The memory now
records that failure and the `gh api` check that reveals whether the
assignment actually took effect.
AI-assisted-by: step-5-preview-free
---
 .serena/memories/workflow/creating-issues.md | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/.serena/memories/workflow/creating-issues.md b/.serena/memories/workflow/creating-issues.md
index 1032606ef4..dbe55c9241 100644
--- a/.serena/memories/workflow/creating-issues.md
+++ b/.serena/memories/workflow/creating-issues.md
@@ -263,6 +263,16 @@ AUTHOR=$(gh pr view <PR_NUMBER> --repo penpot/penpot --json author --jq '.author
 gh issue edit <ISSUE_NUMBER> --repo penpot/penpot --add-assignee "$AUTHOR"
 ```
 
+GitHub only allows assigning users with write permission, org members, or
+users who have already commented on the issue. Assigning an outside
+contributor fails with `422 ... assignees ... invalid`, and `gh issue edit`
+still exits 0 and prints the issue URL. Verify the result and, when the list
+stays empty, skip the assignment:
+
+```bash
+gh api repos/penpot/penpot/issues/<ISSUE_NUMBER> --jq '[.assignees[].login]'
+```
+
 ### Set Issue Type and verify
 
 See the **Setting the Issue Type** and **Verification** sections above — the