I feel --remote is too specific. It only works if the revision to be diffed has one tracking branch. Maybe better to add some revset function/parameter that looks up tracking remote by local revision.

Landed here searching for "how to diff jj remote changes"

I'm trying to replicate my old git flow, and when using git I got into the habit of always doing a git diff '@{upstream}' prior to pushing any actual changes to the remote, to ensure what I was pushing was actually what I intended push (i.e. no secrets or unintended files included).

This is even more relevant for me with jj, given the auto-snapshotting behaviour. Is there absolutely no way (e.g. alias) to do this currently?

I ran into this yesterday and came up with a goofy workaround. I'm sure there's a way to clean it up, and I'm sure there are lots of edge cases around, e.g., multiple bookmarks between main and @, but it is working for me in simple cases.

function curr_bookmark { jj bookmark list --tracked -r 'trunk()..@' -T 'name++"\n"' | head -1 }
alias jdr='jj diff -f "$(curr_bookmark)@origin"'

This is even more relevant for me with jj, given the auto-snapshotting behaviour. Is there absolutely no way (e.g. alias) to do this currently?

Since jj doesn't have a "currently-checked-out branch" (yet?), there's fundamentally no way to ask "what is the current branch" so that you can compare it to its remote counterpart. I think @david-crespo's solution above is the best you can do for now, where you have to heuristically determine what branch you're on.

This is even more relevant for me with jj, given the auto-snapshotting behaviour. Is there absolutely no way (e.g. alias) to do this currently?

Since jj doesn't have a "currently-checked-out branch" (yet?), there's fundamentally no way to ask "what is the current branch" so that you can compare it to its remote counterpart. I think @david-crespo's solution above is the best you can do for now, where you have to heuristically determine what branch you're on.

What you think about jj diff - -branch name - - remote
You will need to type less and you don't need any heuristics. Just diff branch with branch@remote

The point is to not have to figure out and type the bookmark name.

Wrote a script to cover the case of "diff from my local commit to corresponding commit on remote".

#!/usr/bin/env bash
set -eu -o pipefail

target=$1

# todo: configurable stream head
bookmark_names=$(jj log --no-graph -r 'heads(::@ & bookmarks())' -T 'local_bookmarks.map(|l| l.name()).join(" ")')
IFS=" " read -ra bookmarks <<<"$bookmark_names"
# todo: error message
[ ${#bookmarks[@]} -eq 1 ] || exit 1
bookmark=${bookmarks[0]}

all_refs=$(jj evolog --no-graph -T 'commit_id ++ "|"' -r "$target")
# todo: configurable remote
remote=$(jj log --no-graph -T 'commit_id' -n 1 -r "($all_refs none()) & ::$bookmark@origin")

jj diff --from "$remote" --to "$target"

It gets somewhat confused if you split a commit, and you might want to use jj interdiff instead of jj diff. Could also just stop at the bookmark=... line if you just want to jj diff --from bookmark@remote --to bookmark.

I'm was working on a PR to try to fix this. I followed @yuja comment and created a remote revset function. With it, you can do jj diff --from remote(@) --to @

I wrote most of the code a while ago, but didn't get around to finish it due to university and work, but now that I see that more people would like to have this issue fixed, I might have the will to finish it.