Harden ci-autopilot portfolio docs#1965
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c81b55f3ca
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| ## Overview | ||
|
|
||
| ci-autopilot is an AI-powered CI repair agent that monitors GitHub Actions workflows, detects failures, triages them via an issue queue, and dispatches autonomous repairs using a Python agent backed by Codex. It runs on a self-hosted runner and coordinates the full lifecycle from failure detection to merged fix. | ||
| `ci-autopilot` packages the worker/runtime side of the platform. It monitors GitHub Actions workflows, detects failures, triages them via an issue queue, and dispatches autonomous repairs using a Python agent backed by Codex. It runs on a self-hosted runner and provides the execution path from queued repair task to proposed fix. |
There was a problem hiding this comment.
The new boundary wording says this repository provides an execution path from a queued task to a proposed fix, but agent/poll_once.py only lists queued issues and exits; it neither invokes Codex nor creates or proposes a fix. This overstates the currently implemented worker behavior and will mislead readers evaluating or operating the repository.
Useful? React with 👍 / 👎.
|
|
||
| ## Runbook path | ||
|
|
||
| 1. Read [docs/control-plane.md](docs/control-plane.md) for the issue-queue contract with `autopilot-core`. |
There was a problem hiding this comment.
This step describes docs/control-plane.md as the issue-queue contract with autopilot-core, but that document never mentions autopilot-core or defines any cross-repository contract; it only summarizes this repository's own intake pipeline and labels. Readers following the new runbook therefore cannot obtain the promised integration information from the linked document.
Useful? React with 👍 / 👎.
2 participants
Summary