You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|`/claim`|**Anyone**| Self-assigns the issue to you.|
168
+
|`/addlabel <label1> <label2>`|**Anyone**| Adds labels to the issue (e.g. `/addlabel frontend bug`). |
169
+
|`/unassign @username`|**Maintainers Only**| Removes the assignee from an issue.|
170
+
|`/assign @username`|**Maintainers Only**| Manually assigns someone to an issue.|
171
171
172
172
### ⏳ The Inactivity Policy (Assignment Expiry)
173
173
174
174
To keep the project moving, assignments are not permanent.
175
+
175
176
-**The 3-Day Rule:** If an issue has an assignee but sees **no activity for 3 days**, our automated background job will remove the assignment.
176
177
-**What counts as activity?** Posting a comment, opening a linked PR, or a maintainer adding a label.
177
178
-**Why?** It frees up stale issues so other active contributors can pick them up. If your issue expires, you can always `/claim` it again if it's still available!
178
179
179
180
### 💡 GSSoC Contributor Flow
181
+
180
182
1. Find an unassigned open issue you want to work on.
181
183
2. Comment `/claim` to lock it in.
182
184
3. Need labels? Comment `/addlabel good-first-issue` (labels must already exist in the repo).
0 commit comments