Repository navigation
Organize the GitHub interaction design - #267
Closed
nishu-builder wants to merge 3 commits into
Closed
nishu-builder wants to merge 3 commits into
nishu-builder wants to merge 3 commits into
Conversation
nishu-builder
added this pull request to stack #261
September 19, 2026 23:36
Contributor
Author
|
Closing with the rest of stack #261. #300 replaces this; it rewrites the PRs section of design/agent-github.md and points design/stacks.md at it. Generated by Claude Code |
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
1 participant
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.
Creates a GitHub design overview, linked from
design/chat.md, with separate pages for importing, branch publication, stacks, and PRs. Shared token setup lives in the overview, and the detailed pages link back to it.Moves the import and PR instructions out of the mixed documents, fixes the branch API tables, and explains how published stack branches map to PR heads and bases. Stack pushes remain independent of PR creation and GitHub stack membership.
This documentation-only PR sits above #265 so design comments can be reviewed together and applied to the relevant implementation PRs below it.