Auto-Assign PRs when Issue "Lead" set

[mekarpeles]

Feature Request

When a contributor open a PR before we set a Lead on the issue, the PR is unassigned... And then once we set the Lead of the issue, the PR does not get automatically updates (i.e. must be updated manually).

This feature proposes a github action to listen for updating/adding of the Lead label and updating the corresponding PR w/ assignee

Related to #9212

Problem / Opportunity

Proposal

Breakdown

Related files

Refer to this map of common Endpoints:
*

Requirements Checklist

Checklist of requirements that need to be satisfied in order for this issue to be closed:

• [ ]

Stakeholders

---

Instructions for Contributors

• Before creating a new branch or pushing up changes to a PR, please first run these commands to ensure your repository is up to date, as the pre-commit bot may add commits to your PRs upstream.

[SAYAN02-DEV]

Hey @mekarpeles I have worked on this issue I have added a github action workflows
that assigns PR to the issue lead:

The technical flow
Issue Label Added (Lead: @username)
↓
GitHub triggers workflow
↓
Workflow checks: startsWith("Lead:")?
↓ YES
Runs Node.js script with (repo, issue#, label)
↓
Script extracts username from label
↓
Script searches: "repo:X is:pr is:open {issue#} in:body"
↓
For each PR found:
├─ Validate: PR body contains "Closes/Fixes/Resolves #{issue#}"?
├─ Check: Lead already assigned?
└─ If valid & not assigned → POST /assignees API call
↓
PR now has lead as assignee