https://linen.dev logo
Join Slack
Powered by
I’m unable to merge the rest of a stack, starting ...
# report-bugs
m
I’m unable to merge the rest of a stack, starting with app.graphite.com/github/…/49214. I’ve been trying since last night. I’ve tried 
gt sync && gt submit
and retrying. It always fails with “Graphite couldn’t merge this PR because it failed for an unknown reason.”
c
Matt yours is a bit different, can I have you do gt feed -d "for chris" so it can send me out the logs? For t.couzens@relaytech.co I was able to duplicate this, I am writing up a report and exploring some workarounds. Now: dequeue each hung gtmq draft and re-queue its underlying PR so it re-batches on a live base and gets its checks. Prevent: make the merge queue sequential (turn off Parallel CI + Batching). I will check back in once I have a better idea of some more long term fixes. Thanks!
Matt- * gt feedback -d "for chris"
m
✅ I’ve run 
gt feedback -d "for chris"
🙌 1
Is there anything I can do on my side to make the stack mergable again?
👀 1
c
Checking
When Graphite tried to merge #49214, GitHub rejected a base-branch update on the next PR in the stack (#49215) with a validation error about the PR being part of a stack. That surfaces on our side as the generic “failed for an unknown reason” message. Two things that would help us confirm the right unblock path: (1) on GitHub, do these PRs show as part of a GitHub Stack? (2) if you have a repo admin, any stack-related rules or settings they know of. Your local submit path looked healthy — this is specifically the server-side merge/retarget step.
m
1. Yes, on GitHub it shows as part of a GitHub Stack
2. I’m checking
Yeah.. something (possibly my AI coding agent) issued the 
gh stack
command on this stack/segment.
Unstacking on the Github side fixed it
🙌 1
c
Awesome! Let me know if anything else pops up. Thanks!
2 Views
Open in Slack
PreviousNext
Powered by