Guilherme Mendel
06/26/2026, 6:34 PMChris Bowie
06/26/2026, 7:27 PMgraphite-base/1977) rather than your repo’s trunk. Graphite creates those graphite-base/… branches while managing stacked PRs and are not meant to be the final form that should land on trunk.
That can happen when a stack merge or a post-merge retarget step doesn’t fully complete, or when a PR is merged while it still targets graphite-base/*.
To confirm what happened for this PR and the safest recovery, could you send:
1. The full Graphite or GitHub PR URL for the PR that shows as merged into graphite-base/1977
2. Whether you merged via Graphite or on GitHub
3. Whether the changes you expected are on your default branch, or only on that graphite-base ref
Thanks!
Chris