René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"gh stack rebase: queued PR treated as merged, causing incorrect rebases for downstream branches","articleBody":"Reproduction\n\n1. On a repo with stacked branches and PRs queued in the merge queue, run `gh stack rebase`.\n2. Example observed output from a user report:\n\n```\n➜  token-scanning-service git:(aerendel/mixed-content-types3) gh stack rebase\n✓ Fetched origin\n✓ Trunk main fast-forwarded to aed1023\nStack detected: (main) \u003c- aerendel/mixed-content-types1 \u003c- aerendel/mixed-content-types2 \u003c- aerendel/mixed-content-types3\nRebasing branches in order, starting from aerendel/mixed-content-types1 to aerendel/mixed-content-types3\n✓ Skipping aerendel/mixed-content-types1 (PR #9333 queued)\n✓ Rebased aerendel/mixed-content-types2 onto main (adjusted for merged PR)\n✓ Rebased aerendel/mixed-content-types3 onto aerendel/mixed-content-types2 (adjusted for merged PR)\nAll branches in stack rebased locally with main\nTo push up your changes, run `gh stack push`\n```\n\nActual behavior\n\n- `gh stack rebase` treated a queued PR (PR #9333) as if it were merged when computing rebases for subsequent branches. The command skipped the first branch due to it being \"queued\", but then rebased the next branch \"adjusted for merged PR\", and treated the final branch as rebased onto the intermediate branch \"adjusted for merged PR\". This resulted in the second-layer branch being rebased as if the queued PR had already been merged.\n\nExpected behavior\n\n- Queued PRs in the merge queue (not yet merged into trunk) should NOT be treated as merged when computing rebases for downstream branches. `gh stack rebase` should preserve the stack order and rebase subsequent branches relative to the actual trunk and the true merge state (or otherwise clearly document and provide an option to treat queued PRs as merged).\n\nAdditional context\n\n- Command used: `gh stack rebase`\n- Observed in token-scanning-service example above (output pasted by user).\n\nSuggested fix ideas\n\n- Detect PRs that are only queued (not merged) and ensure they are not considered merged when adjusting base refs for downstream rebases.\n- Add a flag or mode to opt-in to \"treat queued PRs as merged\" if there are valid workflows that expect that behavior.\n\nPlease let me know if you need logs or more reproduction details; the user who reported this is the original author of the pasted stack output.\n\n[View original Slack conversation](https://github.slack.com/archives/C09M2GA1KQX/p1782322028230539?thread_ts=1782322028.230539\u0026cid=C09M2GA1KQX)","author":{"url":"https://github.com/skarim","@type":"Person","name":"skarim"},"datePublished":"2026-06-24T17:45:29.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/144/gh-stack/issues/144"}