https://linen.dev logo
Join Slack
Powered by
I'm getting this error: ```📨 Creating/updating PR...
# report-bugs
t
I'm getting this error:
Copy code
📨 Creating/updating PRs...
ERROR: Failed to submit PR for 05-24-replaced_three_payload_heaps_with_a_single_objectheap_class:
🥞 Nice stack! Only opening PRs for the first 50 branches in the stack. To open PRs for the upstack branches, please split up the stack (using gt move) or first merge and close some of the downstack PRs.
Even though the push was actually successful.
There used to be more than 50 open PRs in the stack, but because it didn't want to create more than 50 PRs I merged the 4 bottom ones to have enough space for the whole stack.
So now it does push successfully, but still gives the error
j
Thanks for the extra context. The branch push succeeding is expected here: the push happens first, then Graphite tries to create/update the PRs and checks the open PR count for the full stack. After merging the bottom PRs, could you run 
gt sync
and then retry 
gt submit
? 
gt sync
should clean up the merged branches locally and restack the remaining branches. If it still hits the 50-PR limit after that, please run:`gt feedback --with-debug-context "still hitting 50 branch stack limit after merging bottom PRs and running gt sync"`and we can take a closer look.
t
I already did 
gt sync
and 
gt submit
, so when I did it just now it didn't give an error, since it say 
No-op
for all branches.
And to be clear, it also successfully creates the PRs and show them in the stack in the web interface, it just gave me an error in the console and didn't automatically open the web interface for the new PRs.
I made some changes to one of the commits, so I pushed everything again, that showed the same error, so I used the 
gt feedback
as suggested
j
Hi there, thanks for submitting the feedback. Looks like my colleague responded to your support ticket generated from the feedback cmd`T-D32941`I'll go ahead and close this case to keep a single thread on the new case moving forward.
t
Does that mean you'll keep it open here, or close it here? I don't think your colleague has the context needed
j
Hey again - The connected graph includes two fork points: one around PRs #573/#574 under #572, and another around PRs #697/#699 under #696. Because of those connected sibling PRs, Graphite currently sees 55 PRs in the connected stack graph. Of those, 4 are merged and 1 is closed, leaving exactly 50 open PRs. That’s why the 50-open-PR guard is still firing even though the UI count looks like it should be below the limit. Should this help - to get unblocked, you’ll need to still get the connected stack below 50 open PRs. The quickest path is to merge or close at least one more open PR in that connected stack, then run 
gt sync
and retry 
gt submit --stack
. I agree the CLI/UI explanation here is confusing, especially because some PRs can be created or updated successfully before a later branch hits the limit. I’ll keep that context attached here.
2 Views
Open in Slack
PreviousNext
Powered by