I noticed the Meshery PR queue is high-volume, and I'd like to propose a review-stage taxonomy (needs review / changes requested / ci failing / ready to merge) with automation to help triage — including flagging low-effort or drive-by PR/issue-claim patterns.
I checked the repo and found path-based labeling (labeler.yml) and label-triggered commenting (label-commenter.yml), but nothing yet for review-stage tracking. I'd like to take a scoped pass at this — happy to draft a full spec/issue first if useful, or bring it up at this week's dev meeting.
Thanks,
Darshan