It is not even close to sufficient. jj fix only executes the command on one file at a time (only the changed files) so it can't work on anything that has linter semantics.
jj does this for performance reasons. They don't want to perform a full checkout for every rebase action. This is simply something I disagree with
> jj does this for performance reasons. They don't want to perform a full checkout for every rebase action.
It's true that `jj fix` can be faster by not touching the working copy, but we also want a `jj run` command for the linter feature (https://github.com/jj-vcs/jj/issues/1869). It's just not done yet.
conradludgate|4 months ago
jj does this for performance reasons. They don't want to perform a full checkout for every rebase action. This is simply something I disagree with
martinvonz|4 months ago
It's true that `jj fix` can be faster by not touching the working copy, but we also want a `jj run` command for the linter feature (https://github.com/jj-vcs/jj/issues/1869). It's just not done yet.