Repository navigation
β¨ feat: render native GitHub pull request stacks - #82
Conversation
Co-authored-by: Codex <noreply@openai.com>
|
To use Codex here, create an environment for this repo. |
Co-authored-by: Codex <noreply@openai.com>
|
@codex review |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
βΉοΈ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with π while any review is running, comments if it has suggestions, and reacts with π once all reviews finish with no findings. |
|
Codex Review: Didn't find any major issues. More of your lovely PRs please. Reviewed commit: βΉοΈ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
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". |
Motivation
Native GitHub stacks currently look like unrelated PRs in gh-llm. For a middle layer, that hides its dependencies, confuses the direct diff base with the stack's merge target, and offers ordinary merge commands that do not handle native stack merging.
Changes
pr view --show stack, showing bottom-to-top membership, the current layer, target branch, and each member's draft/review/merge/CI state. Metadata-only views remain lightweight; stack entries are paginated.EXPECTED, including app identity matching.pr checks --allfor closed and merged PRs. Historical checks do not apply today's branch requirements.Cumulative stack diffs and historical stack join/leave reconstruction remain outside this change; the latter's historical stack IDs are not reliably exposed by the API. No gh-stack installation or local stack state is required.
Validation
uv run pytest -q: 128 passed, including 22 new stack/check regression cases.ty check --error-on-warning, Prettier, andgit diff --checkpassed.