Title: Ask rtibblesbot to validate a contributor-opened issue · Issue #114 · learningequality/.github · GitHub
Open Graph Title: Ask rtibblesbot to validate a contributor-opened issue · Issue #114 · learningequality/.github
X Title: Ask rtibblesbot to validate a contributor-opened issue · Issue #114 · learningequality/.github
Description: Overview A contributor opens an issue and nothing checks the claim in it. A maintainer must read the report and check it against the code before the issue can be labelled or worked. When a contributor opens an issue, ask @rtibblesbot to ...
Open Graph Description: Overview A contributor opens an issue and nothing checks the claim in it. A maintainer must read the report and check it against the code before the issue can be labelled or worked. When a contribu...
X Description: Overview A contributor opens an issue and nothing checks the claim in it. A maintainer must read the report and check it against the code before the issue can be labelled or worked. When a contribu...
Opengraph URL: https://github.com/learningequality/.github/issues/114
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Ask rtibblesbot to validate a contributor-opened issue","articleBody":"## Overview\n\nA contributor opens an issue and nothing checks the claim in it. A maintainer must read the\nreport and check it against the code before the issue can be labelled or worked.\n\nWhen a contributor opens an issue, ask `@rtibblesbot` to validate the report, and label the\nissue while the validation runs.\n\n**Complexity:** Medium\n**Target branch:** main\n\n### Context\n\nContributors opened 27 issues across kolibri, studio and kolibri-design-system in the last\nsix months, about five a month. Nine of the twelve still open on kolibri carry no label, so\nthe claim in each was never confirmed or rejected in the open.\n\nThe registry carries no automation for a contributor-opened issue. `issue-open` only swaps the\ncontributing header in the body.\n\nlearningequality/coding-agent#1229 adds the validation on the agent side. It must land first.\nUntil it does, the agent drops a mention on an issue it did not open, so this automation posts\ncomments that nothing answers.\n\nThe design rests on one assumption to check before anything is built: a mention posted with\nthe LE bot app's token reaches `rtibblesbot` as a notification. A mention is the only way to\nreach the agent, because it polls notifications and holds no inbound endpoint. A label creates\nno notification, so the label alone cannot start the work.\n\nOn a claim that holds, the agent also rewrites the issue title and body to correct what the\nreport states wrongly. `manage-issue-header.js` owns the block between `\u003c!---HEADER START-->`\nand `\u003c!---HEADER END-->`, so the agent preserves that block and this side changes nothing. The\nconstraint is stated from the agent's side in learningequality/coding-agent#1229. A body edit\nfires no event this repository listens to, because `issue-label-header` runs on `labeled` and\n`unlabeled` only.\n\n### The change\n\n**A new automation.** Add `issue-validation` to `automation-registry.yml`, on\n`issues: [opened]`, with the leaf `issue-validation.yml` and the script\n`scripts/issue-validation.js`.\n\nIt runs when all of these hold:\n\n- The repository is in `COMMUNITY_REPOS`.\n- The opener is a contributor by `isContributor`, so a core team member and a bot are both\n excluded.\n- The issue does not already carry `community-issue-review`.\n\nIt then posts one comment that mentions `@rtibblesbot`, and adds `community-issue-review`. The\ncomment tells the contributor that the report is under review and what happens next. The add\ncall creates the label in a repository that does not define it, as the\n`community-contribution-in-progress` path already does.\n\n**A second automation to clear the label.** Add `issue-validation-done`, on\n`issue_comment: [created]`. It removes `community-issue-review` when the comment body carries\n`\u003c!-- ISSUE_VALIDATION -->`. The marker is the contract between the two repositories. A check\non the comment author alone is not enough, because `rtibblesbot` comments on issues for other\nreasons. This cannot live in `contributor-issue-comment`, because `rtibblesbot` is in\n`BOT_USERNAMES` and that automation drops a bot comment by design.\n\n**A sweep for the stuck case.** If the agent never answers, because the service is stopped or\nevery token is capped, the label stays on and misleads a maintainer. Add a sweep to\n`unassign-inactive-issues` that removes `community-issue-review` when its `labeled` event is\nolder than `ISSUE_REVIEW_MAX_DAYS` days. Three days is generous, because a healthy agent\nanswers in minutes.\n\n**Constants.** Add the label name, the marker and the age limit to `scripts/constants.js`, and\nadd the comment body beside the other bot messages.\n\n### Out of Scope\n\n- The validation itself, which lives in learningequality/coding-agent#1229.\n- Any label beyond `community-issue-review`.\n- Closing the issue. No automation here triggers a closure, and the agent decides none\n either. The verdict comment names the close it recommends. A maintainer asks for it in a\n reply, and the agent's own resolution path applies it, which accepts only a maintainer's\n ask. So a wrong verdict costs a reply rather than a closed report.\n- Issues opened by core team members.\n- Acting on the verdict, for example assigning the issue or adding `help wanted`.\n- Pull requests. `contributor-pr-reply` already covers them.\n\n### Acceptance Criteria\n\n- [ ] An issue opened by a contributor in a community repo gets one comment mentioning\n `@rtibblesbot`, and the `community-issue-review` label.\n- [ ] An issue opened by a core team member gets neither.\n- [ ] An issue opened by a bot gets neither.\n- [ ] An issue opened in a repository outside `COMMUNITY_REPOS` gets neither.\n- [ ] An issue that already carries the label gets no second comment.\n- [ ] A comment carrying `\u003c!-- ISSUE_VALIDATION -->` removes the label.\n- [ ] A comment without the marker leaves the label on.\n- [ ] The weekly sweep removes the label when it is older than `ISSUE_REVIEW_MAX_DAYS` days,\n and leaves a younger one on.\n- [ ] A failure to add or remove the label does not fail the run, and it is logged.\n- [ ] `node scripts/generate-automation.js --check` passes, so the generated files match the\n registry.\n- [ ] Tests cover each guard: contributor, core member, bot, repository, label already\n present, marker present, marker absent.\n- [ ] `docs/community-automations.md` describes both automations and the marker contract.\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 cases need an account outside the organization.\n\n1. Post a comment mentioning `@rtibblesbot` with the LE bot app's token. Expect a notification\n on the bot account. If none arrives, the whole design needs a different trigger, so run\n this step first.\n2. Open an issue from an account outside the organization. Expect one comment mentioning\n `@rtibblesbot`, and the `community-issue-review` label.\n3. Open an issue as a core team member. Expect no comment and no label.\n4. Post a comment carrying `\u003c!-- ISSUE_VALIDATION -->`. Expect the label to come off.\n5. Post a comment without the marker. Expect the label to stay on.\n6. Reopen the issue from step 2 while the label is on. Expect no second comment.\n7. Backdate a label, or lower `ISSUE_REVIEW_MAX_DAYS`, then run the sweep by\n `workflow_dispatch`. Expect the label to come off.\n\n### References\n\n- learningequality/coding-agent#1229: adds the validation, posts the verdict and owns the\n marker. It must land first.\n- #105 proposes GitHub Discussions as the entry point for unplanned work. That reduces how\n many reports reach this path. It does not replace the check on the ones that do.\n- #111 updates the contributing page to say that a bug report comes before a pull request.\n- `scripts/community-contribution-label.py`: the existing add and remove pattern, and the\n proof that an add creates a label the repository does not define.\n\n## AI usage\n\nI used Claude Code to measure how many issues contributors open and how many were never\nlabelled, and to trace why a mention is the only way to reach the agent. The split between\nthe two repositories and the label are my decision.\n","author":{"url":"https://github.com/akolson","@type":"Person","name":"akolson"},"datePublished":"2026-10-20T09:14:49Z","url":"https://github.com/learningequality/.github/issues/114"}
| 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:edaf2bdf-697e-04b0-b185-29e5a783228f |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | E0AA:1833B7:18D4E0B:21523EC:6AFFF372 |
| html-safe-nonce | 1207651b6c315ac107a837e0df47b49b21d7fc004fbc8ddb9e72a747c61206cb |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJFMEFBOjE4MzNCNzoxOEQ0RTBCOjIxNTIzRUM6NkFGRkYzNzIiLCJ2aXNpdG9yX2lkIjoiNDc5NjgxNTM4NDMxMTIzMTM0NiIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | 8f8d36fbe3c6cc74345226147ec55436737591eb4a82dec5aa1cbf0789020f87 |
| hovercard-subject-tag | issue:5939125420 |
| 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/114/issue_layout |
| twitter:image | https://opengraph.githubassets.com/8eaa676f3215e88167ca7fa2c44f73030f0c539461c26a439d4cb2dbbfff0bc6/learningequality/.github/issues/114 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/8eaa676f3215e88167ca7fa2c44f73030f0c539461c26a439d4cb2dbbfff0bc6/learningequality/.github/issues/114 |
| og:image:alt | Overview A contributor opens an issue and nothing checks the claim in it. A maintainer must read the report and check it against the code before the issue can be labelled or worked. When a contribu... |
| 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