Codex + GitHub issues

Run Codex from a GitHub issue.

Choose a scoped issue. RustGrid gives Codex the repository context, records the run, checks the result, and returns a pull request for you to review.

No automatic merge. You keep the final decision.

One complete run

Issue #247 becomes pull request #251.

A concrete, fictional example of the product path—from an accepted issue through passing checks and a human review queue.

acme/billing · issue #247PR ready

bug

A checkout reservation can be reused after its expiry. Reject it before creating or reusing a Stripe session.

Acceptance: Expired reservations return a conflict and no session is created.
Constraints: Preserve valid retries and existing idempotency behavior.

Issue acceptedRepository and acceptance criteria captured

✓

Codex changed 3 filesExpiry guard, error mapping, regression test

✓

Quality gates passed18 tests · formatter · type checks

✓

Pull request #251 opened+74 −12 · ready for human review

→

Agent summaryExpired reservations now fail before checkout session lookup.

The pull request explains the change, lists validation, and preserves the issue-to-run audit trail.

✓Unit tests18 passed

✓Type checkpassed

·Human reviewwaiting

The working contract

RustGrid keeps the task, execution, validation, and review state connected instead of leaving you to reconstruct the story from a chat transcript.

Context

Repository instructions, issue details, constraints, and acceptance criteria travel into the run.

Execution

See run events, tool activity, validation, failures, and continuation instead of waiting on a black box.

Review

Inspect the diff and checks in GitHub. Merge, request refinement, or close it yourself.

A good first issue

Choose work with a clear repository, expected behavior, and a result your existing checks can evaluate.

Your issue is the starting line

Connect a repository, choose the issue, and review the pull request RustGrid produces.