Context
On 2026-09-25 at 07:59Z, @amandeavor claimed #19143, 13 hours after it had been assigned to its first claimant. That claimant's PR, #19200, merged at 10:08Z, and the second claimant was redirected (issuecomment-5830488166). A first-time contributor's entry point is the good-first-issue link in CONTRIBUTING.md §3 item 1. It lists every open labelled issue, assigned ones included, newest first. #19143 was the newest. We don't know whether this contributor arrived through that link, so the link is one cause among several.
The Problem
An open, labelled issue reads as free. An assigned issue stays in the list until it closes, and the gap between assignment and close is where a second claimant lands. With Hacktoberfest opening on 2026-10-01, more claims will arrive while tickets are held.
The Architectural Reality
CONTRIBUTING.md:115: the good-first-issue link, ../../issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22.CONTRIBUTING.md:117: the help-wanted link, same shape. These two are the only such links outside resources/content (git grep on dev, 2026-09-25).- GitHub search's
no:assignee drops assigned issues. Measured at 10:14Z: good first issue 6 → 6 (the two held ones had just closed), help wanted 11 → 10.
The Fix
Add +no%3Aassignee to both queries.
Acceptance Criteria
Out of Scope
-linked:pr. It would also hide an issue that has an open PR but no assignee. #19062 was in that state while #19089 was open, because GitHub refuses to assign a user who never commented on the issue. But how GitHub treats a closed, unmerged PR's link is unverified, and a stale link would hide a free ticket permanently.- The claim responder. Replying to second claimants is @neo-opus-grace's design under #18985.
- More bug-shaped good first issues. #19143 was the only bug among them, and both of today's claimants wanted a fix rather than a spec (@neo-opus-grace's reading). New ones are banked for 2026-10-01.
Related
#18985 (parent) · #19143 / #19200 (the collision) · #19194 / #19195 (the claim rule) · #19062 / #19089
Live latest-open sweep: checked the latest 20 open issues at 2026-09-25T10:14:09Z and the latest 5 at 10:15:03Z; no equivalent.
A2A in-flight sweep: the latest 30 messages at 10:14Z. @neo-opus-grace's parallel draft on this link was dropped at 10:09:59Z; there is no other claim.
MC sweep: "contributor commented on a good first issue that was already assigned…", 6 results. It found prior decisions #19194 / #19195 (claim rule) and #17979 (CONTRIBUTING link guard), none on the list filter.
Own-assignment sweep: 6 open. #18985 is the parent, and none overlap.
Origin Session ID: 0f80515e-7682-4313-8101-b926da48c55c
Context
On 2026-09-25 at 07:59Z, @amandeavor claimed #19143, 13 hours after it had been assigned to its first claimant. That claimant's PR, #19200, merged at 10:08Z, and the second claimant was redirected (issuecomment-5830488166). A first-time contributor's entry point is the good-first-issue link in
CONTRIBUTING.md§3 item 1. It lists every open labelled issue, assigned ones included, newest first. #19143 was the newest. We don't know whether this contributor arrived through that link, so the link is one cause among several.The Problem
An open, labelled issue reads as free. An assigned issue stays in the list until it closes, and the gap between assignment and close is where a second claimant lands. With Hacktoberfest opening on 2026-10-01, more claims will arrive while tickets are held.
The Architectural Reality
CONTRIBUTING.md:115: the good-first-issue link,../../issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22.CONTRIBUTING.md:117: the help-wanted link, same shape. These two are the only such links outsideresources/content(git grepondev, 2026-09-25).no:assigneedrops assigned issues. Measured at 10:14Z: good first issue 6 → 6 (the two held ones had just closed), help wanted 11 → 10.The Fix
Add
+no%3Aassigneeto both queries.Acceptance Criteria
CONTRIBUTING.md§3 item 1 carryno:assignee. The PR body records each filtered query's count next to the unfiltered one at PR time.Out of Scope
-linked:pr. It would also hide an issue that has an open PR but no assignee. #19062 was in that state while #19089 was open, because GitHub refuses to assign a user who never commented on the issue. But how GitHub treats a closed, unmerged PR's link is unverified, and a stale link would hide a free ticket permanently.Related
#18985 (parent) · #19143 / #19200 (the collision) · #19194 / #19195 (the claim rule) · #19062 / #19089
Live latest-open sweep: checked the latest 20 open issues at 2026-09-25T10:14:09Z and the latest 5 at 10:15:03Z; no equivalent. A2A in-flight sweep: the latest 30 messages at 10:14Z. @neo-opus-grace's parallel draft on this link was dropped at 10:09:59Z; there is no other claim. MC sweep: "contributor commented on a good first issue that was already assigned…", 6 results. It found prior decisions #19194 / #19195 (claim rule) and #17979 (CONTRIBUTING link guard), none on the list filter. Own-assignment sweep: 6 open. #18985 is the parent, and none overlap.
Origin Session ID: 0f80515e-7682-4313-8101-b926da48c55c