Peter Werry
10/20/2025, 8:23 PMmain -> branch 1 -> branch 2, and I merge branch 2 -> branch 1 on github, I always end up in a state in graphite where it doesn’t see or properly sync that merge. After a gt sync, gt checkout displays main -> branch 1 -> branch 2 instead of main -> branch 1
I also see warnings during sync that look like this:
WARNING: Unable to clean up the following branches with merged PRs because their commits are not in main.
WARNING: Not operating on these branches and their descendants:
▸ branch 2
WARNING: To clean up these stacks, ensure main contains the merged PRs in the stack.
What am I doing wrong here?Pylon
10/20/2025, 8:23 PMPeter Werry
10/20/2025, 8:28 PM> gt checkout branch 1
This branch has been updated remotely since you last submitted it.
Last submitted version: v2 (remote at v3).
Run gt get to fetch remote changes.
> gt get
🌲 Fetching branches from remote...
Running git fetch: [========================================] 100% | Done
main is up to date.
WARNING: Unable to clean up the following branches with merged PRs because their commits are not in main.
WARNING: Not operating on these branches and their descendants:
▸ branch 2
WARNING: To clean up these stacks, ensure main contains the merged PRs in the stack.Peter Werry
10/20/2025, 8:37 PMgt pop branch 2 and then re-syncing, but this isn’t ideal. Seems like a bug?Pylon
10/20/2025, 8:39 PMgt sync prompted me to delete the merged branch which the ui showed the changes from both branches in branch 1 diff view. also is there a reason to do this in github instead of using gt fold ?Peter Werry
10/20/2025, 8:40 PMgt --version 1.6.6Pylon
10/20/2025, 8:45 PMgt sync updates since 1.6.6Peter Werry
10/20/2025, 8:46 PMPeter Werry
10/20/2025, 8:46 PM