This PR shouldn't affect unrelated files

Restored - this was deleted accidentally.

There is no need to test constants. The file can be removed.

Removed.

Renamed to ASSIGN_COOLDOWN_DAYS throughout.

It'd be better to remove all these new 'Any' table entries and organize the new information to the original table structure - that is utilizing Core team, Close contributor, Issue creator, and Other categories, and none other. This will improve understanding the information a lot.

Furthermore let's use the following language for describing comment type

• /assign command
• assign keyword (links to https://github.com/learningequality/.github/blob/main/scripts/constants.js#L44)
• regular

Finally, let's not use shortcuts, such as GFI - it's not immediately clear to what it refers to.

Restructured: removed Any** rows, integrated /assign command rows under Close contributor/Issue creator/Other contributor types, updated comment type terminology (regular/assign keyword//assign command), and replaced GFI with good first issue throughout.

Two items missed in the previous pass: split the combined 'Close contributor, Issue creator, Other' rows into separate rows per contributor type (18 rows total — 6 per category), and linked 'assign keyword' to constants.js#L44 throughout the table.

There should be no updates to yarn.lock in this PR. Let's revert completely

Reverted. yarn.lock now matches main exactly.

Can be removed

Removed.

blocking: This fires only on the good first issue labeled event, and good-first-issue-comment.js:27 requires help wanted already present. Tagging GFI before help wanted is valid — a good first issue not yet open. The normal prepare-then-open flow adds help wanted second, so nothing re-runs this check and guidance never posts on issues that just opened. Also trigger on the help wanted labeled event and require both labels in the script before posting; a lone GFI stays silent.

Fixed in 4422dc8. Now triggers on both good first issue labeled and help wanted labeled events. good-first-issue-comment.js already checks for both labels before posting, so a lone GFI label stays silent — guidance only posts when both are present.

suggestion: search.issuesAndPullRequests({ q }) returns only the first 30 results, so an active contributor's unassignments can be missed and the cooldown under-counts. Use github.paginate(github.rest.search.issuesAndPullRequests, { q, per_page: 100 }) and iterate the result directly (drop data.items).

Fixed in 4422dc8. Changed to github.paginate(github.rest.search.issuesAndPullRequests, { q, per_page: 100 }) and iterate the result directly (no data.items).

suggestion: Exact match drops /assign me, which falls through to keyword detection instead of assigning. /\/assign\b/i.test(commentBody) accepts /assign me and please /assign while rejecting /assignee.

Implemented in 4422dc8. Changed to /\/assign\b/i.test(commentBody) — accepts /assign me and please /assign while rejecting /assignee. The plan had exact-match but the regex is clearly better UX.

suggestion: Unrelated trailing-newline strip (accidental reformat in 0d2508a). Revert: git checkout main -- .github/FUNDING.yml.

No change needed — git diff main -- .github/FUNDING.yml shows no diff. The file already matches main (trailing newline is present).

praise: Dedup-by-issue keeping the latest unassignment cleanly handles multiple assign/unassign cycles on one issue.

Glad that reads clearly.

praise: Filtering cooldown entries against currently-assigned issues prevents double-counting a reassigned issue — correct slot math.

Glad that reads clearly.