Repository navigation
Description
❌ This issue is not open for contribution. Visit Contributing guidelines to learn about the contributing process and how to find suitable issues.
Observed behavior
The automations treat members of the Learning Equality code reviewers team as community contributors.
For example, pcenov opened learningequality/kolibri#15827. The issue validation workflow posted its contributor greeting and asked rtibblesbot to validate the issue. pcenov is an active member of learning-equality-code-reviewers, so this should not have happened.
#134 changed maintainer detection to use team membership. MAINTAINER_TEAMS in scripts/constants.js lists only these teams:
le-admins-teamread-only-coding-agentstriaging-coding-agents
learning-equality-code-reviewers is not on the list. Team members who are in none of the three teams fail the maintainer check.
Expected behavior
A member of learning-equality-code-reviewers is a maintainer. The automations do not treat them as a contributor on issues, comments, or pull requests.
Steps to reproduce
- Use an account that is in
learning-equality-code-reviewersand in none of the teams inMAINTAINER_TEAMS. - Open an issue in a repo listed in
ISSUE_VALIDATION_REPOS, for exampletest-actions. - The bot posts the "Thanks for opening this issue!" comment and adds the
community-issue-reviewlabel.
Deliverables
- Members of
learning-equality-code-reviewerspass the maintainer check in every workflow that usesisContributororisMaintainer. - A test in
scripts/is-contributor.test.jscovers a user who is only inlearning-equality-code-reviewers. docs/testing-automations.mdstill describes the maintainer teams correctly.
Technical pointers
scripts/constants.js:MAINTAINER_TEAMSscripts/utils.js:isMaintainerchecks each team withteams.getMembershipForUserInOrg.- Callers of the maintainer check:
scripts/is-contributor.js, which these workflows use:issue-validation,contributor-issue-comment,contributor-pr-reply,pull-request-label,review-requested, andholiday-message.scripts/pull-request-template.jsscripts/update-pr-spreadsheet.js
- Recognise maintainers by team and comment on template check failures #134 notes an open risk: it did not confirm that the app token can read membership of every team. Check this for the new team too.
AI usage
Claude Code drafted this issue from a maintainer's report. It read the code on main, confirmed pcenov's team membership with the GitHub API, and found the workflows that call the maintainer check.

Activity
rtibblesbot commentedon Nov 12, 2026
@bjester I can't verify these acceptance criteria in my sandbox. Tick the ones this PR may skip and reply, or reply naming them. A reviewer checks each skipped one on the PR; the rest stay required.
learning-equality-code-reviewers. — needs a workflow run in alearningequalityrepo with the bot app's tokenWritten by rtibblesbot, an LLM-based coding agent.
bjester commentedon Nov 12, 2026
You can skip verifying the ticked criteria.
bjester commentedon Nov 12, 2026
@rtibblesbot You can skip verifying the ticked criteria.