When graphite freezes PRs, and the PRs have new commits in the server, what

gt log

reports is different from what

git log

reports. I don't know if that is intentional or not, but it is quite confusing as I'm expecting I have locally the commits

gt log

reports. For example:

(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>

Brett, thanks for your quick answer. If the idea of

gt log

when frozen is to show all commits in the PRs regardless if they are locally or not, then it should be clear which commits are local and which ones are not. I'm saying this because since we started using graphite I seldom use the

git

command and rely completely in the

gt

command. And expecting that

gt log

would show me only local commits as

git log

was something I was taking for granted. In other words, if a

gt

command does something that may the user believe the local repo is in a given state when is in another (in this case showing commits that are not local) then it should extremely clear. Thank you.