PR revisions
How `roark revise-pr` responds to feedback on an existing pull request.
Last updated
roark revise-pr 123 --repo owner/repo#Flow
- Fetch PR metadata, unresolved review threads, and relevant PR comments with GitHub GraphQL.
- Exclude prior Roark revision summary comments from planner input.
- Prepare an isolated managed clone workspace and check out the existing PR head branch there. The caller/control checkout stays on its current branch.
- Allocate canonical artifacts under
.roark/runs/pr/<pr-number>/revision-<n>/in the control checkout and mirror them into the revision workspace for agent prompts. - Plan feedback handling in the revision workspace.
- Apply only feedback classified as
must-fix-currentin the revision workspace. - Run one revision reviewer and optional fix/review passes in the revision workspace.
- Run verification in the revision workspace.
- On success, create one revision commit from the revision workspace while excluding
.roarkcontrol-plane artifacts, push to the PR head branch, and post one summary comment from the control checkout.
#Feedback classifications
must-fix-current: required fix for the current PR.already-addressed: feedback already satisfied.needs-human: requires maintainer decision or unavailable context.non-blocking: valid follow-up, not required for this PR.invalid/stale: no longer applicable.
#Safety boundaries
Roark refuses closed PRs, fork PR heads in v1, base/shared branch heads, and dirty control working trees unless --yes is passed. PR checkout, agent edits, review, verification, commit, and push happen in an isolated managed clone workspace under the configured workspace root. needs-human, no-op, and verification-failure outcomes do not commit or push.
Revision workspaces reuse the managed workspace configuration (workspace.root, workspace.cloneRemote, workspace.copyToWorktree) and lifecycle hooks. Clean workspaces may be reused; dirty revision workspaces are rejected so local edits are not overwritten.
#Useful commands
Run with an explicit verification command:
roark revise-pr 123 --repo owner/repo --verify "bun run check"Skip the terminal summary comment:
roark revise-pr 123 --repo owner/repo --no-comment#Next steps
- Use Troubleshooting for no-op revisions.
- Use Artifacts to inspect revision outputs.
- Use CLI reference for options.