(If applicable) To help us repro, please send the following if you haven't already: - PR links, screenshots, and/or debug output if applicable - Repro steps - Does this happen consistently? Just to you or others on your team also? - Is this a regression? Is the problem new? - If you're having an issue with the CLI, please send us debug logs using

gt feedback --with-debug-context <any message>

https://github.com/triumpharcade/go-triumph-backend/pull/5111 vs https://app.graphite.dev/github/pr/triumpharcade/go-triumph-backend/5111

Hey Matthew, definitely an odd one 🤔 looking at the PR metadata is all seems right, is this the only PR experiencing this? quick scan im seeing most others point to

debug

trunk. im wondering if this occured on like

gt init --trunk

somehow.

Multiple PRs are showing this. If this is a configuration issue, where is this configured?

gt config

 ->

repository settings

 ->

trunk branches

 is where this lives locally

This GitHub PR was created by the web UI. Are you saying that local Graphite config affects the process by which Graphite picks up GitHub PRs?

good morning Matthew, I was only suggesting that your local graphite config plays a role in what git commands we issue from

gt

CLI.

This GitHub PR was created by the web UI

Is this Graphite UI github? Would love to understand the workflow here so i can attempt to reproduce it. Also, could you share another graphite that is experiencing the issue? TIA

Yes, the origin PR is the GitHub web UI. Here's another Graphite PR that's hit by the same issue: https://app.graphite.dev/github/pr/triumpharcade/go-triumph-backend/5196/Release

cool, thanks for the clarity here. Just to confirm 2 other points: • so it was created in github UI, then checked out and tracked via

gt

 CLI? • this is not a blocking issue but causing lots of confusion?

It was created in the GitHub UI and then picked up automatically by Graphite (I think we have an integration set up). And yes, it's not blocking, but causing confusion since our release PRs appear to be going to a typo branch

understood. Writing up a bug for this, thanks again~