Repository navigation
chore(greenlight): auto-approve all paths and opt in to the two_humans check - #144
Merged
Merged
Conversation
…s check The file was missing the required auto_approve_paths key, so Greenlight treated it as malformed. Advisory only: the two_humans check is not required in the ruleset yet. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ilyashatalov
approved these changes
Nov 3, 2026
The repo holds example code only. The server hard floor still keeps workflows, greenlight.yml, the prompts and CODEOWNERS human-only. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
hydra-by-douro-labs
Bot
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a
two_humansblock to.github/greenlight.yml. With it, Greenlight posts agreenlight/two-humanscheck on every PR: one human for a PR Greenlight could auto-approve, two for any other PR. The check is not required in the ruleset, so this blocks nothing. Making it required is a separate step..github/greenlight.ymlis on Greenlight's hard floor, so this PR needs a human merge.Fixes a malformed config and opens all paths to auto-approval
The file on
mainhas noauto_approve_pathskey. Greenlight requires it, so the file fails to parse (missing field auto_approve_paths) and Greenlight treats the repo as malformed: it posts no checks here today.This PR adds
auto_approve_paths: ["**"]. The repo holds example code only, so any path may auto-approve. The server's hard floor (HARD_DEFAULT_PATHSin the greenlight deployment) still keeps these paths human-only, whatever this file says:.github/workflows/**.github/greenlight.yml.github/greenlight/prompts/****/CODEOWNERSmachine_users
pyth-ops: Pyth's ops bot user; it merged a PR here in the last 30 days. Also listed on pyth-lazer.No other bot user accounts among the authors and approvers of the last 30 days.
hydra-by-douro-labsis a GitHub App and is excluded on its own.Impact sample
5 PRs merged since 2026-10-03, none by Greenlight. 2 of them had fewer than 2 humans among the author and approvers. With
auto_approve_paths: ["**"], a PR that touches no hard-floor path needs 1 human; a PR that touches one needs 2.Checks
Parsed both files with Greenlight's own
parse_repo_config(dourolabs/prototypesgreenlight/server/src/app/eligibility.rs): the file onmainfails withmissing field auto_approve_paths; the new file loads withenabled=true,auto_approve_paths=[**]andmachine_users=[pyth-ops].🤖 Generated with Claude Code