Did something change where using GitHub to merge P...
# how-do-i
m
Did something change where using GitHub to merge PRs in a stack no longer works? If I do the following: • Merge the first PR in a stack with GitHub • checkout the second PR in the stack locally and run
gt get
Normally it would prompt saying that the first branch was deleted but now it doesn't, version 1.6.8
p
(If applicable) To help us more clearly understand what you're trying to do, please provide additional details about: - Screenshots / debug logs / list of commands you've tried to run so far - Your workflow - Current state
m
it just says branch A does
not need to be restacked on main
even if it's been merged
and
Restacked branch A on main
but branch A no longer exists on the remote
p
hey Martin, will test this behavior. There hasn't been an intentional change on our end that I'm aware of, but in general we'd advise against merging stacks via GitHub manually
m
did you find anything here, @Gareth Brickman?
p
hey Martin, we tested and could not reproduce that and got the prompt to delete the merged branch. Could you try upgrading your CLI to
1.7.0
to see if it still occurs then?
m
yes, i'll try 👍
it seemed to work earlier today but now it happened again: i merged the first PR manually, and now i'm trying to open a new PR after the first one has already merged. if I run
gt get
it still thinks the first, old, branch is there and doesn't prompt me to remove it. if I run
gt submit
it tries to submit the first PR too.
I think I submitted this PR in the GitHub UI, does that not work anymore perhaps?
hm yeah it seems to be reproducible by opening the PR outside of graphite and then merging it. i'm 99% sure that used to work before
p
hey Martin, something that came to mind: when you say you merged in GitHub was that just a generic merge in the PR or did it perhaps use GitHub's merge queue?
m
no, just a regular merge, no merge queue. sometimes i'll use the "update branch" button to merge in main.