Yuya Nishihara

fwiw, `rebase` avoids this problem by requiring `-d`/`--destination` flag. I agree the current default isn't useful, but I don't know if it's good idea to add special case for the...

> We will need to traverse the `oplog` to find eligible commits. For the default backend, we can iterate the index to get all commits reachable from the op log....

I have no idea why the backtrace contains something named `git`, but the panicking location is here: https://github.com/martinvonz/jj/blob/f00f7527ddce21886fe93e11324c5227f15eeaca/cli/src/cli_util.rs#L1750-L1753 It implies that the file named `.jj/repo/op_store/operations/{op_id}` is somehow lost. (it might...

> `jj debug workingcopy` is printing the exact same error. Right. `jj debug workingcopy --ignore-working-copy` will probably work.

> `-r` and `-p` just accept multiple values, very simple :) I think the problem is that flags taking multiple values aren't so common (or at least, I'm not used...

I slightly prefer shell aliases than `jj-` lookup in `PATH`, but I don't know why modern tools like `cargo` do that. fwiw, shell aliases could be faked if we had...

> What do you mean by "shell aliases could be faked"? By `jj util exec`, do you mean executing a command in the repo root as opposed to anywhere? Yes,...

> what benefit does that have over running things in path? it seems more annoying to setup because of the boilerplate. * alias commands can be inlined in config file...

I mean `jj` (not `jj `). It's a bit annoying that `git` doesn't insert space because there are many `git-` extension commands which are supposed to be executed as `git...

I think a warning is good as the user can simply `jj undo`. Interactive prompt is sometimes annoying.