This message was deleted.
# how-do-is
Slackbot
01/16/2024, 2:13 PMThis message was deleted.
✅ 1
a
Aryaman
01/16/2024, 2:14 PMI'd recommend doing this locally and then resubmitting the affected stacks.
Aryaman
01/16/2024, 2:15 PMSo let's say you have A -> B -> C and want to detach B.
Copy code
$ gt move -o `main` --source B
$ gt checkout B && gt submit --stack
$ gt checkout A && gt submit --stackAryaman
01/16/2024, 2:16 PMsubmita
Ambroos Vaes
01/16/2024, 2:19 PMaha, ok, let's see
Ambroos Vaes
01/16/2024, 2:24 PM@Aryaman it looks like that doesn't work when A is already merged and no longer exists locally.
Ambroos Vaes
01/16/2024, 2:25 PMMy branch B is already directly on main, but in the web UI it shows up as being on top of the previously merged A
a
Aryaman
01/16/2024, 2:26 PMOut of curiosity, why does it matter if a merged PR is in the stack or not?
a
Ambroos Vaes
01/16/2024, 2:27 PMIt's just a visual thing I guess. I'd like to have my stack be cleanly related to a single project for historical purposes. I just happen to have worked on a separate utility commit in between that's not really related to the stack. Now it clutters up the stack when browsing through it. Definitely a minor thing.
a
Aryaman
01/16/2024, 2:30 PMThe ability to hide merged & closed PRs from the stack viz is coming soon, so ideally should become even more minor going forward
👍 1
5 Views