github gh-stack Discussions
Pinned Discussions
Discussions
-
You must be logged in to vote Allow "Merge without waiting for requirements to be met (bypass rules)"
feature requestFeature Requests topic: bypass rulesNo 'bypass rules and merge' / admin override for blocked stacked PRs in the web merge box. -
You must be logged in to vote Rebase on partial merge shouldn't automatically dismiss approvals
feature requestFeature Requests topic: approvalsRebasing a stack dismisses downstream approvals, forcing re-review. -
You must be logged in to vote Stacked PRs with branches across forks
feature requestFeature Requests topic: forksSupport stacked PRs with branches across forks. -
You must be logged in to vote Don't automatically rebase
feature requestFeature Requests topic: rebase alternativeAvoid rewriting/force-pushing on restack; cascading-merge alternative to auto-rebase. -
You must be logged in to vote Stacks should have auto-merge capability
feature requestFeature Requests topic: auto-mergeAuto-merge / merge-when-ready for stacks, including enqueue before CI passes. -
You must be logged in to vote gh stack add should allow for adding existing branches
feature requestFeature Requests topic: cli - add`gh stack add`: adopt existing branches, init from a non-stack branch, `-A` committing to main. -
You must be logged in to vote -
You must be logged in to vote -
You must be logged in to vote Feature request: support cascading merge (similar to the cascading rebase)
feature requestFeature Requests topic: rebase alternativeAvoid rewriting/force-pushing on restack; cascading-merge alternative to auto-rebase. -
You must be logged in to vote Approvals are lost on stack rebase with master
feature requestFeature Requests topic: approvalsRebasing a stack dismisses downstream approvals, forcing re-review. -
You must be logged in to vote Add "only mergeable as a full stack" option?
topic: mergeMerging a stack from the UI hangs, gets stuck, or fails; partial-merge and auto-merge breakage. feature requestFeature Requests -
You must be logged in to vote -
You must be logged in to vote Rebasing an out of date stack produces unverified rebase commit
bugBug Reports topic: commit signingPartial merges and rebases produce unsigned or unverified commits. -
You must be logged in to vote Partial merges of stack PRs in the UI produces unsigned commits
bugBug Reports topic: commit signingPartial merges and rebases produce unsigned or unverified commits. -
You must be logged in to vote Stack equivalent of
questiongh pr update-branch --rebaseQuestions & Help topic: cli - rebase`gh stack rebase` behavior and bugs: --upstack, interactive/fixup, hangs, squash-merge handling. -
You must be logged in to vote -
You must be logged in to vote How should contributions from outside GitHub be submitted? (fork pull requests are refused)
questionQuestions & Help topic: docsgh-stack documentation site issues (e.g. broken dark mode). -
You must be logged in to vote Some repos does not support stacks. Which ones?
questionQuestions & Help topic: enablementEnablement and access: repo not enabled, onboarding, PAT/GHES availability, can't create a stack. -
You must be logged in to vote -
You must be logged in to vote Footer ends up in squashed commit messages
topic: cli - submit`gh stack submit`: remote/SSH handling, config flags, draft PRs, and submit UX or failures. feature requestFeature Requests -
You must be logged in to vote Link to stack / stack URL
feature requestFeature Requests topic: stack linkA dedicated shareable stack URL and stack-level description. -
You must be logged in to vote Design issue: stacked PRs should merge to separate target (e.g.
feature requestmain), not base (e.g.feat/1)Feature Requests topic: uiWeb UI for stacks: merge box, sticky stack map, PR-list grouping, per-PR status, navigation. -
You must be logged in to vote Author email of (squash-)merged PRs is merger’s email, not PR author’s email
bugBug Reports topic: merge commitSquash/merge commit contents: mangled or uneditable messages and wrong author email. -
You must be logged in to vote Allow renaming a stack branch without rebasing
topic: cli - modify`gh stack modify`: failures on pruned/untracked files, per-op flags, renaming, terminal keys. feature requestFeature Requests -
You must be logged in to vote Branching stacked pull requests (multiple chains with shared base)
feature requestFeature Requests topic: branching stacksNon-linear stacks: multiple descendants, diamond stacks, trunk as another stack's base.
