Problem
Contributors need to distinguish how urgent an issue is, whose response a PR needs, and whether the project has agreed to maintain the proposed change. The contribution guide defines type and topic labels, but not priority or PR next-step labels.
For example, an author answering a review request should prompt a fresh decision about whose action is next, rather than leave the PR waiting on its author solely because an old request-changes review remains.
Changes
Document a shared triage process in CONTRIBUTING.md:
- Separate scope agreement, urgency, and the next actor. Triage is not implementation acceptance or a delivery promise.
- Define
p0/p1/p2priorities andawaiting-review/awaiting-author/blockedPR labels, with drafts preserved and specific requests or blockers recorded. - Distinguish review status, check results, release delivery, and verified resolution.
This is a documentation-only proposal for agreement before rollout. It does not create or apply labels, add automation, or promise response times.
Activity
3
auto-maintain[bot]9d ago🤖 auto-maintain review
Automated, advisory triage for @privatenumber's PR. Facts below are read from the GitHub API.
| Check | Result |
|---|---|
| Author's merged PRs (this repo) | 27 |
| Account established | ✅ (age 5506d · 3980 followers · 276 public repos) |
| Commits signed/verified | ✅ 1/1 |
| Changeset included | ⚠️ |
Review panel: 🟢 low highest severity
just-bash maintainer code review: 🟢 low
No actionable issues found in the documentation-only triage policy changes.
General code review: 🟢 low
No actionable issues found in the documentation-only triage guidance.
Adversarial security: 🟢 low
Documentation-only triage guidance introduces no actionable security concerns.
Adversarial security (second opinion): 🟢 low
Documentation-only change: a single commit adding triage/priority/PR-label guidance to CONTRIBUTING.md, all plain ASCII with no hidden or non-printable characters, no code, CI, dependency, or install-script modifications, and no new executable, network, or filesystem behavior; the content matches the stated intent and introduces no security-relevant attack surface.
Standard Bash and host portability: 🟢 low
No Bash or host-portability issues; the change is documentation-only.
Posted by auto-maintain. This automated code review is advisory; a human maintainer makes the call.
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment