Repository navigation
Closed
Copy link
Labels
Description
Background
Nacos currently lacks a formal issue claiming process. Contributors express interest via comments, but there is no standardized mechanism to track who is working on what. This leads to:
- Duplicate work: e.g., [Bug] maintainer-client: ParamUtil reports misleading value when timeout/retry properties are invalidย #14875 โ one person commented to claim, the issue author submitted their own PR Use original property strings in NumberFormatException messages for tโฆย #14881, and a third contributor also submitted a fix [ISSUE #14875] Fix misleading error messages in maintainer-client ParamUtilย #14892. Three people worked on the same simple bug.
- Stale claims: Contributors comment "I'd like to work on this" but never follow up, leaving the issue in limbo.
- No visibility: Without GitHub Assignees, it's hard to filter which issues are available vs. already claimed.
Industry Research
| Project | Mechanism | Timeout | Automation |
|---|---|---|---|
| Kubernetes | /assign command via Prow Bot |
90d stale โ 30d rotten โ close | Heavy (Prow) |
| React | Comment + CONTRIBUTING.md rules | 14 days | None (maintainer-enforced) |
| VS Code | help wanted label + manual assign |
7d info-needed | Light |
| Rust | @rustbot claim |
Triagebot managed | Medium |
| Spring Boot | ideal-for-contribution label |
14d feedback | Light |
| Dubbo / RocketMQ | No formal process | N/A | None |
Key takeaway: 14-day timeout is industry consensus. Documentation-first approach (React model) is low-cost and effective for mid-size communities.
Proposal
1. Add "Issue Assignment" section to CONTRIBUTING.md
## Issue Assignment
### How to claim an issue
- Comment on the issue expressing your intent (e.g., "I'd like to work on this")
- Briefly describe your approach so maintainers can provide early feedback
- Wait for a maintainer to assign the issue to you
### Expectations after claiming
- Submit a PR within **14 days** of being assigned
- If you need more time, comment on the issue to let others know
- If no PR or update is provided within 14 days, the issue may be unassigned
and made available for other contributors
### Tips
- Check if an issue already has an assignee before claiming
- For complex issues, consider discussing your approach before starting
- It's okay to unassign yourself if you can't continue โ just leave a comment2. Use GitHub Assignees
When a maintainer confirms a claim, set the GitHub Assignee (not just reply in comments). Benefits:
- Issue list visually shows claim status
- Filter unclaimed issues with
no:assignee - Prevents duplicate claiming
3. (Optional, future) Lightweight automation
If the community grows, consider adding a GitHub Action for:
/assigncomment command โ auto-set assignee- 14-day timeout โ auto-unassign + notify
This is not needed initially โ the documentation + Assignee approach is sufficient.
Activity
KomachiSion commentedon Apr 9, 2026
Great idea, the assign before is depend maintainer and robot.
might be we can do this by ai and github action.
Please first change the imformation in
CONTRIBUTING.mdand I will try auto-assign with ai.you can help to research the bot or github action.
cxhello commentedon Apr 9, 2026
Thanks for the feedback! Here's the progress and plan:
Current Progress
/assigncommand usage once the Action is ready.Implementation Plan
Phase 1: Command-based auto-assign (in progress)
A GitHub Action workflow (
issue-assign.yml) with two functions:/assignto self-assign,/unassignto release. Runs viaissue_commenttrigger, no maintainer intervention needed.stale-assignmentlabelPhase 2: AI intent recognition (future)
Extend Phase 1 to detect natural language claiming intent (e.g., "I'd like to work on this", "ๆๆณ่ฎค้ข่ฟไธช") without requiring a fixed
/assigncommand. This can be added as a branch in the existing workflow โ when a comment doesn't match/assignor/unassign, pass it to an LLM to classify intent.Will submit the Phase 1 PR soon.
[ISSUE #14898] Add issue auto-assign workflow with /assign command anโฆ
Sync develop to new it branch (#14929)