Title: [WIP] Block self-assignment for a cooldown after an inactivity removal · Issue #127 · learningequality/.github · GitHub
Open Graph Title: [WIP] Block self-assignment for a cooldown after an inactivity removal · Issue #127 · learningequality/.github
X Title: [WIP] Block self-assignment for a cooldown after an inactivity removal · Issue #127 · learningequality/.github
Description: Overview The weekly sweep unassigns a contributor for inactivity. The contributor comments /assign and the bot assigns them again within hours. The removal carries no weight, and a contributor who was waiting loses the issue. Block self-...
Open Graph Description: Overview The weekly sweep unassigns a contributor for inactivity. The contributor comments /assign and the bot assigns them again within hours. The removal carries no weight, and a contributor who ...
X Description: Overview The weekly sweep unassigns a contributor for inactivity. The contributor comments /assign and the bot assigns them again within hours. The removal carries no weight, and a contributor who ...
Opengraph URL: https://github.com/learningequality/.github/issues/127
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[WIP] Block self-assignment for a cooldown after an inactivity removal","articleBody":"## Overview\n\nThe weekly sweep unassigns a contributor for inactivity. The contributor comments `/assign` and\nthe bot assigns them again within hours. The removal carries no weight, and a contributor who was\nwaiting loses the issue.\n\nBlock self-assignment for a cooldown period after the bot removes a contributor for inactivity.\nDuring the cooldown, only a maintainer can assign them. The block covers every issue in the\ncommunity repos, not only the issue they left.\n\n### Context\n\nOn learningequality/kolibri#14261, a maintainer unassigned a contributor on 2026-10-23 at 13:07\nUTC. Someone else asked for the issue the next morning. At 05:04 UTC the removed contributor\nasked to be assigned again, the bot replied \"Comment `/assign` to assign yourself\", and at 05:07\nthe bot assigned them. The maintainer removed them a second time on 2026-10-26.\n\n`scripts/contributor-issue-comment.js` reads recent unassignments and adds them to the\nassignment count instead of blocking:\n\n```js\nconst totalSlots = assignedIssues.length + filteredUnassignments.length;\nif (totalSlots >= MAX_ASSIGNED_ISSUES) { ... }\n```\n\n`MAX_ASSIGNED_ISSUES` is 2, so one removal leaves a free slot and `/assign` passes.\n\n`getRecentUnassignments` in `scripts/utils.js` reads `event.assignee.login` and ignores\n`event.actor.login`, so it cannot tell who removed the contributor.\n\nTwo bot messages send the contributor back. `BOT_MESSAGE_KEYWORD_GOOD_FIRST_ISSUE` tells any\ncontributor to comment `/assign`, and the unassignment comment in\n`scripts/unassign-inactive-issues.js` says \"please message us here, and we'll assign you again\".\n\n### The Change\n\n**Classify each unassignment by actor.** Return `unassignedBy` from `event.actor.login`:\n\n| Actor | Meaning | Effect |\n| --- | --- | --- |\n| The contributor | Self-drop | Consumes a slot, as it does today |\n| `learning-equality-bot[bot]` | Inactivity removal | Starts the cooldown |\n| Anyone else | Not an inactivity removal | No cooldown |\n\nUnassignment for inactivity belongs to the sweep, so the bot is the actor and no marker is\nneeded. A maintainer using the assignee menu starts no cooldown, because that removal was not\nfor inactivity.\n\n**Block `/assign` during the cooldown.** Check it in `handleAssignCommand` before the limit\ncheck. A block is not a slot, and the issue the contributor left is no exception. Only a\nmaintainer can assign them during the cooldown, by hand.\n\n**Add `REMOVAL_COOLDOWN_DAYS` to `scripts/constants.js`,** set to 7.\n`getRecentUnassignments` takes the longer of the two windows, and each rule reads its own.\n\n**Add a block message** that names the days remaining and says that a maintainer can assign them\nby hand. Send `BOT_MESSAGE_KEYWORD_GOOD_FIRST_ISSUE` only to a contributor who is not under\ncooldown, and reword the unassignment comment to name the cooldown instead of promising\nre-assignment.\n\n### Out of Scope\n\n- Changing `MAX_ASSIGNED_ISSUES`, `ASSIGN_COOLDOWN_DAYS`, or the 30-day inactivity threshold.\n- Blocking an assignment that a maintainer makes by hand.\n- What counts as inactivity. That is #128.\n\n### Acceptance Criteria\n\n- [ ] A contributor whom the bot removed for inactivity within the cooldown cannot self-assign\n the issue they left, or any other issue in a community repo.\n- [ ] A maintainer can assign a contributor under cooldown by hand.\n- [ ] A removal by a maintainer through the assignee menu starts no cooldown.\n- [ ] A self-drop keeps the current behaviour, that is it consumes a slot and does not block.\n- [ ] Once the cooldown expires, `/assign` works again.\n- [ ] The block message names the days remaining and does not tell the contributor to comment\n `/assign`.\n- [ ] The bot does not post `BOT_MESSAGE_KEYWORD_GOOD_FIRST_ISSUE` to a contributor under\n cooldown.\n- [ ] The unassignment comment names the cooldown and promises no re-assignment.\n\n### Testing\n\nTest in `test-actions`. See\n[testing the automations](https://github.com/learningequality/.github/blob/main/docs/testing-automations.md).\nThe contributor cases need an account outside the organization.\n\n1. Label an issue `help wanted` and `good first issue`, then comment `/assign` from the\n contributor account. Expect an assignment.\n2. Dispatch the sweep so that the bot unassigns the contributor, then comment `/assign` again.\n Expect a refusal that names the days remaining.\n3. Comment `/assign` on a second `good first issue`. Expect the same refusal.\n4. Assign the contributor by hand. Expect the assignment to hold.\n5. Unassign the contributor through the assignee menu, then comment `/assign`. Expect an\n assignment, because a maintainer removal starts no cooldown.\n6. Unassign yourself from the contributor account, then comment `/assign` on a second issue.\n Expect an assignment, because one slot is free.\n\n### References\n\nThe real case is learningequality/kolibri#14261. #128 fixes what the sweep counts as inactivity,\nand this issue depends on it, because the sweep is the actor that starts the cooldown.\n\n## AI usage\n\nI used Claude Code to read the assignment gate, to trace the timeline of kolibri#14261, and to\nconfirm that `getRecentUnassignments` ignores the actor. I decided that the cooldown blocks\nrather than consumes a slot, that it covers every issue, and that only an inactivity removal by\nthe bot starts it.\n","author":{"url":"https://github.com/akolson","@type":"Person","name":"akolson"},"datePublished":"2026-10-26T17:09:51Z","url":"https://github.com/learningequality/.github/issues/127"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:02ddd607-3b34-c748-39f1-2bd6f8820adb |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | EE0C:B0403:D8CB56:11A036F:6AFFEC81 |
| html-safe-nonce | 73f248a3287b3e8065b69a08f1385bdd64fc5a842df3453d4857a1667ac428eb |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJFRTBDOkIwNDAzOkQ4Q0I1NjoxMUEwMzZGOjZBRkZFQzgxIiwidmlzaXRvcl9pZCI6IjM2MTQ0NTUwNzg2NDA5MzgxMTMiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ== |
| visitor-hmac | 2c39d8a80a17d933dc113ae63a1a3271d1966b033d953ba45c86a3bb84c72b0a |
| hovercard-subject-tag | issue:6044532437 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/learningequality/.github/127/issue_layout |
| twitter:image | https://opengraph.githubassets.com/65138fabbe3850b32d0e41bcd0275160bcb0f648cf137c798a273d9880e38c7e/learningequality/.github/issues/127 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/65138fabbe3850b32d0e41bcd0275160bcb0f648cf137c798a273d9880e38c7e/learningequality/.github/issues/127 |
| og:image:alt | Overview The weekly sweep unassigns a contributor for inactivity. The contributor comments /assign and the bot assigns them again within hours. The removal carries no weight, and a contributor who ... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | akolson |
| hostname | github.com |
| expected-hostname | github.com |
| None | 0a0d8686a27478df474dd7415776a7a080cde8838b3cd92ea7601187572e5729 |
| turbo-cache-control | no-preview |
| go-import | github.com/learningequality/.github git https://github.com/learningequality/.github.git |
| octolytics-dimension-user_id | 3926525 |
| octolytics-dimension-user_login | learningequality |
| octolytics-dimension-repository_id | 647407699 |
| octolytics-dimension-repository_nwo | learningequality/.github |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 647407699 |
| octolytics-dimension-repository_network_root_nwo | learningequality/.github |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 16a11879678aaf97e2a42c33ee70830aa084fa37 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width