You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
No revision path when an upstream maintainer requests changes on a filed PR #60
openai/openai-agents-python#4890 was filed from run 20260906T104815Z-29582c.
A maintainer reviewed it and requested changes. Mailman has no stage for that.
The run's terminal state is READY_FOR_HUMAN_REVIEW, then the operator files
the PR and the record stops. There is no state, no command and no section of mailman/procedure.md covering "an upstream reviewer asked for changes on a
filed PR". mailman --help lists nothing between prepare-submission and retrospective that accepts maintainer feedback as input.
Impact
Every maintainer-requested revision is hand-driven: an operator reads the
review, edits the workspace directly and pushes. That loses the two properties
the harness exists to provide.
No reviewer pass. The revision that answers a maintainer goes upstream with
less scrutiny than the original, which had a full primary/reviewer cycle.
No record. run.json still says READY_FOR_HUMAN_REVIEW with human_decision: null while the PR has moved two states past it. The
retrospective and the contribution ledger both read from that record.
A revision is also where a run is most likely to go wrong: the maintainer has
named a constraint, and an agent working without the review text in its prompt
will not honour it.
mailman/maintainer_review.py reads the upstream review into the run, RunStatus.MAINTAINER_CHANGES_REQUESTED gives the run somewhere to move, and check_revision refuses to call the revision done until each requested change has an answer. CLI: mailman maintainer-review. Covered by tests/test_maintainer_review.py. Verified on main at 59da1d6.
Activity
wip: pre-screen issues, refresh ready candidates, and read maintainer…
wolfgang-aura commentedon Sep 10, 2026
mailman/maintainer_review.pyreads the upstream review into the run,RunStatus.MAINTAINER_CHANGES_REQUESTEDgives the run somewhere to move, andcheck_revisionrefuses to call the revision done until each requested change has an answer. CLI:mailman maintainer-review. Covered bytests/test_maintainer_review.py. Verified onmainat 59da1d6.