IssueRaiser

[Announcement] 📢 New Workflow: Requirement to be assigned to issues before opening PRs

## 📢 New Workflow: Requirement to be assigned to issues before opening PRs We’re thrilled by the passion of the community and want to respect your time and effort in contributing. As community contributions grow, we’ve noticed an increase in duplicate Pull Requests for the same issue. To ensure that no one spends time on a fix that someone else is already handling, we are implementing an Issue Assignment policy. ### 🛠 How the New Process Works 1. **Identify an Issue:** Raise an issue or find an existing issue that interest you. 2. **Claim it:** Leave a comment (e.g., *"I'd like to take this on!"*). 3. **Wait for the Badge:** A maintainer will assign the issue to you in 24 hours. 4. **Ship it:** Once assigned, feel free to submit your PR. > **Note:** PRs submitted for unassigned issues may be delayed or closed if someone else was already officially assigned to the task. ### 🕒 The "5-Day" Momentum Rule We want to keep the project moving. If an issue is assigned but sees **no activity (PR or status update) for 5 days**, it will be unassigned to allow other contributors a chance to help. We understand life happens—just drop a quick comment if you need more time! ### ⚡ Exceptions (fast-track + Code-First) While the assignment system helps us stay organized, we don’t want it to slow down obvious improvements. You are welcome to submit a Pull Request without prior assignment for:* **Documentation:** Fixing typos or clarifying instructions. * **Micro-fixes:** Minor tweak

Posted by RichardTang-Aden on Jan 26, 2026, 1:22 AM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments

reliability (Other)

[Announcement] 📢 New Workflow: Requirement to be assigned to issues before opening PRs

RichardTang-AdenJan 26, 2026, 1:22 AM

## 📢 New Workflow: Requirement to be assigned to issues before opening PRs We’re thrilled by the passion of the community and want to respect your time and effort in contributing. As community contributions grow, we’ve noticed an increase in duplicate Pull Requests for the same issue. To ensure that no one spends time on a fix that someone else is already handling, we are implementing an Issue Assignment policy. ### 🛠 How the New Process Works 1. **Identify an Issue:** Raise an issue or find an existing issue that interest you. 2. **Claim it:** Leave a comment (e.g., *"I'd like to take this on!"*). 3. **Wait for the Badge:** A maintainer will assign the issue to you in 24 hours. 4. **Ship it:** Once assigned, feel free to submit your PR. > **Note:** PRs submitted for unassigned issues may be delayed or closed if someone else was already officially assigned to the task. ### 🕒 The "5-Day" Momentum Rule We want to keep the project moving. If an issue is assigned but sees **no activity (PR or status update) for 5 days**, it will be unassigned to allow other contributors a chance to help. We understand life happens—just drop a quick comment if you need more time! ### ⚡ Exceptions (fast-track + Code-First) While the assignment system helps us stay organized, we don’t want it to slow down obvious improvements. You are welcome to submit a Pull Request without prior assignment for:* **Documentation:** Fixing typos or clarifying instructions. * **Micro-fixes:** Minor tweak

Comments (0)

No comments yet. Start the discussion.

Comment on this issue