Steve Fink
b6686114be
The problem is that a jj change with a conflict is represented as a dummy git patch with a set of empty directories. When `git diff HEAD` processes a branch containing such a commit, it thinks that every file in the repo was changed. With this patch, things still won't go well if you try to run `mach clang-format` when your patch stack is based on a conflict, but that's a kind of weird thing to do. (It's reasonable to get a conflict, `jj new <conflict>`, fix it, then run `mach clang-format` with the intention of reformatting the fixed tree, which previously broke.) Differential Revision: https://phabricator.services.mozilla.com/D262707
29 lines
393 B
TOML
29 lines
393 B
TOML
[DEFAULT]
|
|
subsuite = "mozversioncontrol"
|
|
|
|
["test_branch.py"]
|
|
|
|
["test_commit.py"]
|
|
|
|
["test_context_manager.py"]
|
|
|
|
["test_diff_stream.py"]
|
|
|
|
["test_get_commits.py"]
|
|
|
|
["test_get_commit_patches.py"]
|
|
|
|
["test_get_mozilla_remote_args.py"]
|
|
|
|
["test_get_upstream_remotes.py"]
|
|
|
|
["test_push_to_try.py"]
|
|
|
|
["test_try_commit.py"]
|
|
|
|
["test_update.py"]
|
|
|
|
["test_workdir_outgoing.py"]
|
|
|
|
["test_working_directory.py"]
|