This message was deleted.
# how-do-i
s
This message was deleted.
a
Not currently possible, but we have wanted to build this! I'll take a look into how difficult it is to implement and let you know if we can make this happen.
👍 1
g
Thanks for the quick response.
A related question, how can I see the changes introduced by a single version of a single PR? For example, I expected the view I get from the choice in the screenshot should be equivalent to
git show bf4c5b7
or something like it. Asked in reverse, given the selection in the screenshot, what is the equivalent e.g.
git diff foo..bar
to get the same view?
j
The version diffing view is currently not working properly — the fix will land later today, but what you have selected should be showing you that (
git diff c8918e3 bf4c5b7
)
g
Ah, that is super helpful info. Thanks for the quick reply. The info I get from
git diff c8918e3 bf4c5b7
doesn't make a lot of sense (seems to contain totally unrelated changes). Is it possible that the commit hashes are also bogus?
Can I get the info from the
gt
CLI ?
gt log
shows the commits that are currently part of the PR, but not the history
j
ah I see — yes, this also includes the rebase changes. we don't currently have a command that shows you the "diff of diffs" like the UI does
you may be able to simulate it with
git range-diff
g
Thanks for the pointer. I need to learn about that command. In the meantime, let me check that I understand. My notional model for
git diff foo bar
is that it's a diff between the contents of the results of
git checkout foo
and
git checkout bar
. But if the parent of
bar
is
main
whereas the parent of
foo
is
main~30
, when I will see "unrelated" changes.
j
that's correct
our UI handles this case by showing the difference between
main~30
and
main
in a different color than the changes between
foo
and
bar
👍 1
g
So I tried
Copy code
git range-diff main..c8918e3 main..bf4c5b7
and I understand it's output, I think. Cool! I am not sure how I would use it to give the output I was looking for, which is "what changed between v9 and v10 of this PR"
a
@Gustavo Nunes Goretkin the versions indicator should be working again FYI. Apologies for the down time.
✅ 1