📚 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
This commit is contained in:
Andrey Antukh 2026-10-09 17:14:05 +00:00
parent 25e8f349e1
commit da2652f1dd

View File

@ -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