René's URL Explorer Experiment


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

direct link

Domain: github.com


Hey, it has json ld scripts:
{"@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-profiling0
react-import-mapreact,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-controllervoltron_issues_fragments
route-actionissue_layout
fetch-noncev2:edaf2bdf-697e-04b0-b185-29e5a783228f
current-catalog-service-hash81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114
request-idE0AA:1833B7:18D4E0B:21523EC:6AFFF372
html-safe-nonce1207651b6c315ac107a837e0df47b49b21d7fc004fbc8ddb9e72a747c61206cb
visitor-payloadeyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJFMEFBOjE4MzNCNzoxOEQ0RTBCOjIxNTIzRUM6NkFGRkYzNzIiLCJ2aXNpdG9yX2lkIjoiNDc5NjgxNTM4NDMxMTIzMTM0NiIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9
visitor-hmac8f8d36fbe3c6cc74345226147ec55436737591eb4a82dec5aa1cbf0789020f87
hovercard-subject-tagissue:5939125420
github-keyboard-shortcutsrepository,issues,copilot
google-site-verificationApib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I
octolytics-urlhttps://collector.github.com/github/collect
analytics-location///voltron/issues_fragments/issue_layout
fb:app_id1401488693436528
apple-itunes-appapp-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/learningequality/.github/114/issue_layout
twitter:imagehttps://opengraph.githubassets.com/8eaa676f3215e88167ca7fa2c44f73030f0c539461c26a439d4cb2dbbfff0bc6/learningequality/.github/issues/114
twitter:cardsummary_large_image
og:imagehttps://opengraph.githubassets.com/8eaa676f3215e88167ca7fa2c44f73030f0c539461c26a439d4cb2dbbfff0bc6/learningequality/.github/issues/114
og:image:altOverview 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:width1200
og:image:height600
og:site_nameGitHub
og:typeobject
og:author:usernameakolson
hostnamegithub.com
expected-hostnamegithub.com
None0a0d8686a27478df474dd7415776a7a080cde8838b3cd92ea7601187572e5729
turbo-cache-controlno-preview
go-importgithub.com/learningequality/.github git https://github.com/learningequality/.github.git
octolytics-dimension-user_id3926525
octolytics-dimension-user_loginlearningequality
octolytics-dimension-repository_id647407699
octolytics-dimension-repository_nwolearningequality/.github
octolytics-dimension-repository_publictrue
octolytics-dimension-repository_is_forkfalse
octolytics-dimension-repository_network_root_id647407699
octolytics-dimension-repository_network_root_nwolearningequality/.github
turbo-body-classeslogged-out env-production page-responsive
disable-turbofalse
browser-stats-urlhttps://api.github.com/_private/browser/stats
browser-errors-urlhttps://api.github.com/_private/browser/errors
release16a11879678aaf97e2a42c33ee70830aa084fa37
ui-targetfull
theme-color#1e2327
color-schemelight dark
react-app-nameissues

Links:

Skip to contenthttps://github.com/learningequality/.github/issues/114#start-of-content
https://github.com/
Sign inhttps://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Flearningequality%2F.github%2Fissues%2F114
GitHubRepository hosting, code review, and collaborationhttps://github.com/platform
CopilotAI coding agent for tasks, projects, and automated workhttps://github.com/features/copilot
ActionsCI/CD and automationhttps://github.com/features/actions
Code QualityQuality analysis, fixes, and enforcementhttps://github.com/features/code-quality
CodespacesCloud development environmentshttps://github.com/features/codespaces
Code SecurityVulnerability detection and remediationhttps://github.com/security/advanced-security/code-security
Secret ProtectionSecret scanning and leak preventionhttps://github.com/security/advanced-security/secret-protection
All Featureshttps://github.com/features
Documentationhttps://docs.github.com/en
Traininghttps://learn.github.com/skills
Certificationshttps://learn.github.com/credentials
Build with Copilothttps://github.com/features/ai
Customize Copilothttps://docs.github.com/en/copilot/how-tos/copilot-on-github/customize-copilot/customize-copilot-overview
Integrationshttps://github.com/marketplace
Trending reposhttps://github.com/trending
GitHub Sponsorshttps://github.com/open-source/sponsors
Developer articleshttps://github.com/resources/articles
ChangelogYour source for the latest features, improvements, and fixes across GitHub products, all in one place.https://github.blog/changelog/
Enterpriseshttps://github.com/enterprise
Teamhttps://github.com/team
Startupshttps://github.com/enterprise/startups
Nonprofitshttps://github.com/solutions/industry/nonprofits
Healthcarehttps://github.com/solutions/industry/healthcare
Financial serviceshttps://github.com/solutions/industry/financial-services
Manufacturinghttps://github.com/solutions/industry/manufacturing
Governmenthttps://github.com/solutions/industry/government
See all industrieshttps://github.com/solutions/industry
Why GitHubhttps://github.com/why-github
Customer Storieshttps://github.com/customer-stories
Business insightshttps://github.com/solutions/executive-insights
Trust Centerhttps://github.com/trust-center
GitHub Advanced SecurityEnterprise-grade code securityhttps://github.com/security/advanced-security
Copilot for businessEnterprise-grade AI featureshttps://github.com/features/copilot/copilot-business
Premium SupportEnterprise-grade 24/7 supporthttps://github.com/enterprise/premium-support
Documentationhttps://docs.github.com/en
Resource centerhttps://github.com/resources
Bloghttps://github.blog/
Events & webinarshttps://github.com/resources/events
Community Forumhttps://github.com/orgs/community/discussions
Customer Storieshttps://github.com/customer-stories
Integrationshttps://github.com/marketplace
Customer supporthttps://help.github.com/
Traininghttps://learn.github.com/skills
GitHub Statushttps://www.githubstatus.com/
Abouthttps://github.com/about
Partnershttps://github.com/partners
Changeloghttps://github.blog/changelog/
GitHub UniverseThe event for developers, by developers — talks, workshops, and what’s next for GitHub.https://githubuniverse.com/
Pricinghttps://github.com/pricing
Sign inhttps://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Flearningequality%2F.github%2Fissues%2F114
Sign uphttps://github.com/signup?ref_cta=Sign+up&ref_loc=header+logged+out&ref_page=%2F%3Cuser-name%3E%2F%3Crepo-name%3E%2Fvoltron%2Fissues_fragments%2Fissue_layout&source=header-repo&source_repo=learningequality%2F.github
Reloadhttps://github.com/learningequality/.github/issues/114
Reloadhttps://github.com/learningequality/.github/issues/114
Reloadhttps://github.com/learningequality/.github/issues/114
learningequalityhttps://github.com/learningequality
.githubhttps://github.com/learningequality/.github
Codehttps://github.com/learningequality/.github
Issues10 (10)https://github.com/learningequality/.github/issues
Pull requests1 (1)https://github.com/learningequality/.github/pulls
Actionshttps://github.com/learningequality/.github/actions
Projectshttps://github.com/learningequality/.github/projects
Security and qualityhttps://github.com/learningequality/.github/security
Insightshttps://github.com/learningequality/.github/insights
https://github.com/learningequality/.github
New issuehttps://github.com/login?return_to=https://github.com/learningequality/.github/issues/114
New issuehttps://github.com/login?return_to=https://github.com/learningequality/.github/issues/114
#126https://github.com/learningequality/.github/pull/126
Ask rtibblesbot to validate a contributor-opened issuehttps://github.com/learningequality/.github/issues/114#top
#126https://github.com/learningequality/.github/pull/126
github_actionsPull requests that update GitHub Actions codehttps://github.com/learningequality/.github/issues?q=state%3Aopen%20label%3A%22github_actions%22
OSC Automationshttps://github.com/learningequality/.github/milestone/1
https://github.com/akolson
akolsonhttps://github.com/akolson
on Oct 20, 2026https://github.com/learningequality/.github/issues/114#issue-5939125420
testing the automationshttps://github.com/learningequality/.github/blob/main/docs/testing-automations.md
[Proposal] Set up GitHub Discussions as the entry point for unplanned work #105https://github.com/learningequality/.github/issues/105
Update the contributing page to indicate that a bug report comes before the pull request #111https://github.com/learningequality/.github/issues/111
akolsonhttps://github.com/akolson
github_actionsPull requests that update GitHub Actions codehttps://github.com/learningequality/.github/issues?q=state%3Aopen%20label%3A%22github_actions%22
on Oct 20, 2026https://github.com/learningequality/.github/issues/114#event-33727113719
akolsonhttps://github.com/akolson
OSC Automationshttps://github.com/learningequality/.github/milestone/1
on Oct 20, 2026https://github.com/learningequality/.github/issues/114#event-33729136240
rtibbleshttps://github.com/rtibbles
completedhttps://github.com/learningequality/.github/issues?q=is%3Aissue%20state%3Aclosed%20archived%3Afalse%20reason%3Acompleted
#126https://github.com/learningequality/.github/pull/126
on Nov 2, 2026https://github.com/learningequality/.github/issues/114#event-34948382136
Sign up for freehttps://github.com/signup?return_to=https://github.com/learningequality/.github/issues/114
Sign in to commenthttps://github.com/login?return_to=https://github.com/learningequality/.github/issues/114
github_actionsPull requests that update GitHub Actions codehttps://github.com/learningequality/.github/issues?q=state%3Aopen%20label%3A%22github_actions%22
OSC AutomationsNo due datehttps://github.com/learningequality/.github/milestone/1
https://github.com
Termshttps://docs.github.com/site-policy/github-terms/github-terms-of-service
Privacyhttps://docs.github.com/site-policy/privacy-policies/github-privacy-statement
Securityhttps://github.com/security
Statushttps://www.githubstatus.com/
Communityhttps://github.community/
Docshttps://docs.github.com/
Contacthttps://support.github.com?tags=dotcom-footer

Viewport: width=device-width


URLs of crawlers that visited me.