AI agent · GitHub Issue to release
From a GitHub Issue to a tagged release
The endpoint is a tagged release, not a pull request. Label one concrete Issue ai-ready; Orbi writes the code, opens a PR, runs an independent review, merges only the reviewed head, then tags and publishes the GitHub Release for the milestone.
THE DELIVERY LINE
Six steps from Issue to release
This is the GitHub-native workflow described in the Orbi workflow.
- 01 · LABELMark the Issue
ai-readyThe label puts one Issue into the delivery queue.
- 02 · IMPLEMENTClaim it and implement in an isolated worktree
Orbi takes the Issue and writes the change away from the shared checkout.
- 03 · OPEN A PROpen the pull request
The implementation becomes a normal GitHub PR with its evidence.
- 04 · REVIEWIndependently review the Issue’s acceptance criteria
A separate review session can repair the branch and rerun tests.
- 05 · MERGE GATEMerge only when CI is green, the head is unchanged, and the base is current
The gate protects the exact reviewed head.
- 06 · RELEASETag and publish a Release by milestone
The release flow turns the completed milestone into a tagged GitHub Release.
PUBLIC EVIDENCE
A real Issue became a reviewed change
See the public evidence page for Issue #1328, its Issue, and the resulting PR #1331.
START WITH A GOOD CONTRACT
Write an ai-ready Issue
Describe one runtime outcome and acceptance criteria someone can check. Avoid a project plan or a pile of unrelated wishes: the Issue is the contract the implementation and independent review use. The 12 factors for an ai-ready Issue show what to include.
If the result cannot be checked, Orbi cannot safely decide whether it is done.
FAQ
Questions before you hand over an Issue
Will it merge unreviewed code?
No. It merges only the head that passed independent review; see the merge gate guide.
Which models?
Pi supports an OpenAI-compatible API or a Codex subscription. Claude Code is not supported.
What does it cost?
Self-hosted Orbi is free; model usage is yours. See costs for Cloud.
Is it open source?
Yes, under AGPL-3.0.
ISSUE IN, RELEASE OUT
Give the agent a clear finish line
Use GitHub as the queue, ledger, review record, and release record.