Task Summary
Improve assignee handling on issues and PRs so that (a) PRs always have an obvious owner and (b) closed issues always reflect who actually shipped the fix.
Behavior
For PRs — auto-assign the author when the PR is opened, reopened, or moved to ready-for-review. Skip bots (e.g. dependabot[bot]) and PRs that already have an assignee.
For issues — do not auto-assign on creation. New issues stay unassigned and keep the existing triage label (handled by issue-triage.yml) because triage is a deliberate human decision; auto-assigning the reporter would short-circuit it.
On PR merge — when a PR is merged that closes one or more issues (via Closes #N / Fixes #N / Resolves #N keywords or the sidebar "Linked issues" relationship), assign the PR author to those issues, replacing any existing assignees. This gives credit to whoever actually shipped the work — e.g. if A was originally assigned to issue X but B steps in and lands the fix, B becomes the assignee on X when the PR merges.
Why
- New PRs from external contributors currently have no clear owner, slowing review routing.
- Closed-by-PR issues sometimes still show an outdated assignee (the original triager) rather than the person who shipped, which makes credit and history less useful.
- Triage shouldn't be skipped by auto-assigning the reporter — leaving issues unassigned keeps the triage workflow doing its job.
Priority
P2 – Medium
Task Type
Task Summary
Improve assignee handling on issues and PRs so that (a) PRs always have an obvious owner and (b) closed issues always reflect who actually shipped the fix.
Behavior
For PRs — auto-assign the author when the PR is opened, reopened, or moved to ready-for-review. Skip bots (e.g.
dependabot[bot]) and PRs that already have an assignee.For issues — do not auto-assign on creation. New issues stay unassigned and keep the existing
triagelabel (handled byissue-triage.yml) because triage is a deliberate human decision; auto-assigning the reporter would short-circuit it.On PR merge — when a PR is merged that closes one or more issues (via
Closes #N/Fixes #N/Resolves #Nkeywords or the sidebar "Linked issues" relationship), assign the PR author to those issues, replacing any existing assignees. This gives credit to whoever actually shipped the work — e.g. if A was originally assigned to issue X but B steps in and lands the fix, B becomes the assignee on X when the PR merges.Why
Priority
P2 – Medium
Task Type