Skip to content

Commit

Permalink
undo: preserve git-tracking refs in colocated repos by default
Browse files Browse the repository at this point in the history
  • Loading branch information
ilyagr committed Jun 30, 2023
1 parent bdd74db commit 5cefd54
Show file tree
Hide file tree
Showing 4 changed files with 28 additions and 18 deletions.
4 changes: 4 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -161,6 +161,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
[#697](https://github.com/martinvonz/jj/issues/697),
[#1608](https://github.com/martinvonz/jj/issues/1608)

* In colocated repos, a bug causing conflicts when undoing branch moves (#922)
has been fixed. Some surprising behaviors related to undoing `jj git push` or
`jj git fetch` remain.

## [0.7.0] - 2023-02-16

### Breaking changes
Expand Down
22 changes: 14 additions & 8 deletions src/commands/operation.rs
Original file line number Diff line number Diff line change
Expand Up @@ -206,15 +206,19 @@ fn view_with_desired_portions_restored(
new_view
}

fn process_what_arg(what_arg: &[UndoWhatToRestore]) -> BTreeSet<UndoWhatToRestore> {
fn process_what_arg(
what_arg: &[UndoWhatToRestore],
colocated: bool,
) -> BTreeSet<UndoWhatToRestore> {
if !what_arg.is_empty() {
what_arg.iter().cloned().collect()
} else {
btreeset!(
UndoWhatToRestore::Repo,
UndoWhatToRestore::RemoteTracking,
UndoWhatToRestore::GitTracking
)
let mut default_what =
btreeset!(UndoWhatToRestore::Repo, UndoWhatToRestore::RemoteTracking);
if !colocated {
default_what.insert(UndoWhatToRestore::GitTracking);
}
default_what
}
}

Expand All @@ -225,6 +229,7 @@ pub fn cmd_op_undo(
) -> Result<(), CommandError> {
let mut workspace_command = command.workspace_helper(ui)?;
let bad_op = workspace_command.resolve_single_op(&args.operation)?;
let repo_is_colocated = workspace_command.working_copy_shared_with_git();
let parent_ops = bad_op.parents();
if parent_ops.len() > 1 {
return Err(user_error("Cannot undo a merge operation"));
Expand All @@ -242,7 +247,7 @@ pub fn cmd_op_undo(
let new_view = view_with_desired_portions_restored(
tx.repo().view().store_view(),
tx.base_repo().view().store_view(),
process_what_arg(&args.what),
process_what_arg(&args.what, repo_is_colocated),
);
tx.mut_repo().set_view(new_view);
tx.finish(ui)?;
Expand All @@ -257,12 +262,13 @@ fn cmd_op_restore(
) -> Result<(), CommandError> {
let mut workspace_command = command.workspace_helper(ui)?;
let target_op = workspace_command.resolve_single_op(&args.operation)?;
let repo_is_colocated = workspace_command.working_copy_shared_with_git();
let mut tx = workspace_command
.start_transaction(&format!("restore to operation {}", target_op.id().hex()));
let new_view = view_with_desired_portions_restored(
target_op.view().store_view(),
tx.base_repo().view().store_view(),
process_what_arg(&args.what),
process_what_arg(&args.what, repo_is_colocated),
);
tx.mut_repo().set_view(new_view);
tx.finish(ui)?;
Expand Down
6 changes: 2 additions & 4 deletions tests/test_git_colocated.rs
Original file line number Diff line number Diff line change
Expand Up @@ -374,10 +374,8 @@ fn test_git_colocated_squash_undo() {
// TODO: There should be no divergence here; 2f376ea1478c should be hidden
// (#922)
insta::assert_snapshot!(get_log_output_divergence(&test_env, &repo_path), @r###"
◉ qpvuntsmwlqt 2f376ea1478c A master !divergence!
│ @ rlvkpnrzqnoo 8f71e3b6a3be
│ ◉ qpvuntsmwlqt a86754f975f9 A HEAD@git !divergence!
├─╯
@ rlvkpnrzqnoo 8f71e3b6a3be
◉ qpvuntsmwlqt a86754f975f9 A master HEAD@git
◉ zzzzzzzzzzzz 000000000000
"###);
}
Expand Down
14 changes: 8 additions & 6 deletions tests/test_undo.rs
Original file line number Diff line number Diff line change
Expand Up @@ -199,27 +199,29 @@ fn test_git_push_undo_colocated() {

// Undo the push
test_env.jj_cmd_success(&repo_path, &["op", "restore", &pre_push_opid]);
// === Before auto-import ====
// === Before auto-export ====
// | jj refs | jj's | git
// | | git | repo
// | |tracking|
// ------------------------------------------
// local `main` | BB | BB | BB
// remote-tracking | AA | AA | BB
// === After automatic `jj git import` ====
// remote-tracking | AA | BB | BB
// === After automatic `jj git export` ====
// | jj refs | jj's | git
// | | git | repo
// | |tracking|
// ------------------------------------------
// local `main` | BB | BB | BB
// remote-tracking | BB | BB | BB
// remote-tracking | AA | AA | AA
test_env.advance_test_rng_seed_to_multiple_of(100_000);
test_env.jj_cmd_success(&repo_path, &["describe", "-m", "CC"]);
test_env.jj_cmd_success(&repo_path, &["git", "fetch"]);
// This currently gives an identical result to `test_git_push_undo_import`
// This seems like an OK behavior: `jj` forgot that the remote-tracking branch
// was undone, but keeps track of the latest local version. TODO: Would this
// be improved if `jj git export` exported remote-tracking branches?
insta::assert_snapshot!(get_branch_output(&test_env, &repo_path), @r###"
main: 0a3e99f08a48 CC
@origin (ahead by 1 commits, behind by 1 commits): 8c05de152218 BB
@origin (ahead by 1 commits, behind by 1 commits): 0cffb6146141 AA
"###);
}

Expand Down

0 comments on commit 5cefd54

Please sign in to comment.