Add GitHub PR write actions to the Inbox - #1
Merged
Merged
Conversation
This was referenced Sep 15, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds GitHub pull request write actions to the Inbox, on top of the existing read/review surfaces.
addPullRequestReviewcall withComment/Approve/Request changes. Request changes requires a review body; approve is disabled on your own PR.ghruns.Rust commands wrap the authenticated
ghCLI (existing patterns); no new dependencies and no new auth path.Implementation notes
GitHubWorkItemDetailsgainsid,state,isDraft,mergeable,mergeStateStatus,labels,assignees,reviewRequests(all optional to keep tracker details typechecking);GithubPrDetailsis the required shape for PR actions.cwd:numberfor the session; the review bar is keyed to reset its dialog after a successful publish.UnifiedDiffView, redirected from chat to the pending review via a newonLineCommentprop. Default behavior is unchanged when the prop is absent.gh pr merge/close/reopen/editare silent on success, so those calls allow empty stdout while still surfacing failures.Tests
npm run check:web— 226 files / 2379 tests passed,tsc --noEmitclean.npm run check:rust— fmt clean, clippy-D warningsclean, 310 tests passed.prReview.test.ts(draft, gating, persistence),PrReviewBar.test.ts(bar + inline edit + request handling),PrActions.test.ts(gating, merged state),githubPrWrite.test.ts(invoke payloads), Rustpr_merge_args/pr_edit_flags/pr_state_args/pr_review_payloadtests.Pending before merge