2022-11-26 23:57:50 +00:00
|
|
|
// Copyright 2022 The Jujutsu Authors
|
2022-04-13 13:43:54 +00:00
|
|
|
//
|
|
|
|
// Licensed under the Apache License, Version 2.0 (the "License");
|
|
|
|
// you may not use this file except in compliance with the License.
|
|
|
|
// You may obtain a copy of the License at
|
|
|
|
//
|
|
|
|
// https://www.apache.org/licenses/LICENSE-2.0
|
|
|
|
//
|
|
|
|
// Unless required by applicable law or agreed to in writing, software
|
|
|
|
// distributed under the License is distributed on an "AS IS" BASIS,
|
|
|
|
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
|
|
// See the License for the specific language governing permissions and
|
|
|
|
// limitations under the License.
|
|
|
|
|
|
|
|
use std::path::Path;
|
|
|
|
|
|
|
|
use crate::common::TestEnvironment;
|
|
|
|
|
|
|
|
pub mod common;
|
|
|
|
|
|
|
|
fn create_commit(test_env: &TestEnvironment, repo_path: &Path, name: &str, parents: &[&str]) {
|
|
|
|
if parents.is_empty() {
|
2022-11-05 01:49:56 +00:00
|
|
|
test_env.jj_cmd_success(repo_path, &["new", "root", "-m", name]);
|
2022-04-13 13:43:54 +00:00
|
|
|
} else {
|
2022-08-31 05:39:32 +00:00
|
|
|
let mut args = vec!["new", "-m", name];
|
2022-04-13 13:43:54 +00:00
|
|
|
args.extend(parents);
|
|
|
|
test_env.jj_cmd_success(repo_path, &args);
|
|
|
|
}
|
2022-11-04 04:14:41 +00:00
|
|
|
std::fs::write(repo_path.join(name), format!("{name}\n")).unwrap();
|
2022-06-06 03:23:01 +00:00
|
|
|
test_env.jj_cmd_success(repo_path, &["branch", "create", name]);
|
2022-04-13 13:43:54 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
#[test]
|
|
|
|
fn test_rebase_invalid() {
|
|
|
|
let test_env = TestEnvironment::default();
|
|
|
|
test_env.jj_cmd_success(test_env.env_root(), &["init", "repo", "--git"]);
|
|
|
|
let repo_path = test_env.env_root().join("repo");
|
|
|
|
|
|
|
|
create_commit(&test_env, &repo_path, "a", &[]);
|
|
|
|
create_commit(&test_env, &repo_path, "b", &["a"]);
|
|
|
|
|
|
|
|
// Missing destination
|
2022-11-18 20:50:39 +00:00
|
|
|
let stderr = test_env.jj_cmd_cli_error(&repo_path, &["rebase"]);
|
|
|
|
insta::assert_snapshot!(stderr, @r###"
|
2023-03-17 23:14:20 +00:00
|
|
|
error: the following required arguments were not provided:
|
2022-11-18 20:50:39 +00:00
|
|
|
--destination <DESTINATION>
|
|
|
|
|
|
|
|
Usage: jj rebase --destination <DESTINATION>
|
|
|
|
|
2023-03-17 23:14:20 +00:00
|
|
|
For more information, try '--help'.
|
2022-11-18 20:50:39 +00:00
|
|
|
"###);
|
2022-04-13 13:43:54 +00:00
|
|
|
|
|
|
|
// Both -r and -s
|
2022-11-18 20:50:39 +00:00
|
|
|
let stderr =
|
|
|
|
test_env.jj_cmd_cli_error(&repo_path, &["rebase", "-r", "a", "-s", "a", "-d", "b"]);
|
|
|
|
insta::assert_snapshot!(stderr, @r###"
|
2023-03-17 23:14:20 +00:00
|
|
|
error: the argument '--revision <REVISION>' cannot be used with '--source <SOURCE>'
|
2022-11-18 20:50:39 +00:00
|
|
|
|
|
|
|
Usage: jj rebase --destination <DESTINATION> --revision <REVISION>
|
|
|
|
|
2023-03-17 23:14:20 +00:00
|
|
|
For more information, try '--help'.
|
2022-11-18 20:50:39 +00:00
|
|
|
"###);
|
2022-04-13 13:43:54 +00:00
|
|
|
|
2022-04-13 17:53:50 +00:00
|
|
|
// Both -b and -s
|
2022-11-18 20:50:39 +00:00
|
|
|
let stderr =
|
|
|
|
test_env.jj_cmd_cli_error(&repo_path, &["rebase", "-b", "a", "-s", "a", "-d", "b"]);
|
|
|
|
insta::assert_snapshot!(stderr, @r###"
|
2023-03-17 23:14:20 +00:00
|
|
|
error: the argument '--branch <BRANCH>' cannot be used with '--source <SOURCE>'
|
2022-11-18 20:50:39 +00:00
|
|
|
|
|
|
|
Usage: jj rebase --destination <DESTINATION> --branch <BRANCH>
|
|
|
|
|
2023-03-17 23:14:20 +00:00
|
|
|
For more information, try '--help'.
|
2022-11-18 20:50:39 +00:00
|
|
|
"###);
|
2022-04-13 17:53:50 +00:00
|
|
|
|
2022-04-13 13:43:54 +00:00
|
|
|
// Rebase onto descendant with -r
|
|
|
|
let stderr = test_env.jj_cmd_failure(&repo_path, &["rebase", "-r", "a", "-d", "b"]);
|
2022-04-28 23:32:18 +00:00
|
|
|
insta::assert_snapshot!(stderr, @r###"
|
2022-12-21 04:47:10 +00:00
|
|
|
Error: Cannot rebase 2443ea76b0b1 onto descendant 1394f625cbbd
|
2022-04-28 23:32:18 +00:00
|
|
|
"###);
|
2022-04-13 13:43:54 +00:00
|
|
|
|
|
|
|
// Rebase onto descendant with -s
|
|
|
|
let stderr = test_env.jj_cmd_failure(&repo_path, &["rebase", "-s", "a", "-d", "b"]);
|
2022-04-28 23:32:18 +00:00
|
|
|
insta::assert_snapshot!(stderr, @r###"
|
2022-12-21 04:47:10 +00:00
|
|
|
Error: Cannot rebase 2443ea76b0b1 onto descendant 1394f625cbbd
|
2022-04-28 23:32:18 +00:00
|
|
|
"###);
|
2022-04-13 13:43:54 +00:00
|
|
|
}
|
|
|
|
|
2022-04-13 17:53:50 +00:00
|
|
|
#[test]
|
|
|
|
fn test_rebase_branch() {
|
|
|
|
let test_env = TestEnvironment::default();
|
|
|
|
test_env.jj_cmd_success(test_env.env_root(), &["init", "repo", "--git"]);
|
|
|
|
let repo_path = test_env.env_root().join("repo");
|
|
|
|
|
|
|
|
create_commit(&test_env, &repo_path, "a", &[]);
|
|
|
|
create_commit(&test_env, &repo_path, "b", &["a"]);
|
|
|
|
create_commit(&test_env, &repo_path, "c", &["b"]);
|
|
|
|
create_commit(&test_env, &repo_path, "d", &["b"]);
|
|
|
|
create_commit(&test_env, &repo_path, "e", &["a"]);
|
|
|
|
// Test the setup
|
2022-05-29 23:46:47 +00:00
|
|
|
insta::assert_snapshot!(get_log_output(&test_env, &repo_path), @r###"
|
2023-02-09 02:53:47 +00:00
|
|
|
@ e
|
2023-03-15 03:37:56 +00:00
|
|
|
│ ◉ d
|
|
|
|
│ │ ◉ c
|
2023-02-09 02:53:47 +00:00
|
|
|
│ ├─╯
|
2023-03-15 03:37:56 +00:00
|
|
|
│ ◉ b
|
2023-02-09 02:53:47 +00:00
|
|
|
├─╯
|
2023-03-15 03:37:56 +00:00
|
|
|
◉ a
|
|
|
|
◉
|
2022-04-13 17:53:50 +00:00
|
|
|
"###);
|
|
|
|
|
|
|
|
let stdout = test_env.jj_cmd_success(&repo_path, &["rebase", "-b", "c", "-d", "e"]);
|
2022-04-28 23:32:18 +00:00
|
|
|
insta::assert_snapshot!(stdout, @r###"
|
|
|
|
Rebased 3 commits
|
|
|
|
"###);
|
2022-05-29 23:46:47 +00:00
|
|
|
insta::assert_snapshot!(get_log_output(&test_env, &repo_path), @r###"
|
2023-03-15 03:37:56 +00:00
|
|
|
◉ d
|
|
|
|
│ ◉ c
|
2023-02-09 02:53:47 +00:00
|
|
|
├─╯
|
2023-03-15 03:37:56 +00:00
|
|
|
◉ b
|
2023-02-09 02:53:47 +00:00
|
|
|
@ e
|
2023-03-15 03:37:56 +00:00
|
|
|
◉ a
|
|
|
|
◉
|
2022-04-13 17:53:50 +00:00
|
|
|
"###);
|
2023-02-19 03:31:48 +00:00
|
|
|
|
|
|
|
// Test rebasing multiple branches at once
|
|
|
|
test_env.jj_cmd_success(&repo_path, &["undo"]);
|
|
|
|
let stdout = test_env.jj_cmd_success(&repo_path, &["rebase", "-b=e", "-b=d", "-d=b"]);
|
|
|
|
insta::assert_snapshot!(stdout, @r###"
|
|
|
|
Rebased 2 commits
|
|
|
|
Working copy now at: 9ca2a1544e5d e
|
2023-04-29 05:01:31 +00:00
|
|
|
Parent commit : 1394f625cbbd b
|
2023-02-19 03:31:48 +00:00
|
|
|
Added 1 files, modified 0 files, removed 0 files
|
|
|
|
"###);
|
|
|
|
insta::assert_snapshot!(get_log_output(&test_env, &repo_path), @r###"
|
2023-03-15 03:37:56 +00:00
|
|
|
◉ d
|
2023-02-19 03:31:48 +00:00
|
|
|
│ @ e
|
|
|
|
├─╯
|
2023-03-15 03:37:56 +00:00
|
|
|
│ ◉ c
|
2023-02-19 03:31:48 +00:00
|
|
|
├─╯
|
2023-03-15 03:37:56 +00:00
|
|
|
◉ b
|
|
|
|
◉ a
|
|
|
|
◉
|
2023-02-19 03:31:48 +00:00
|
|
|
"###);
|
|
|
|
|
2023-07-25 17:17:36 +00:00
|
|
|
// Same test but with more than one revision per argument
|
2023-02-19 03:31:48 +00:00
|
|
|
test_env.jj_cmd_success(&repo_path, &["undo"]);
|
2023-07-25 17:17:36 +00:00
|
|
|
let stderr = test_env.jj_cmd_failure(&repo_path, &["rebase", "-b=e|d", "-d=b"]);
|
2023-02-19 03:31:48 +00:00
|
|
|
insta::assert_snapshot!(stderr, @r###"
|
|
|
|
Error: Revset "e|d" resolved to more than one revision
|
|
|
|
Hint: The revset "e|d" resolved to these revisions:
|
|
|
|
e52756c82985 e
|
|
|
|
514fa6b265d4 d
|
2023-07-25 16:07:03 +00:00
|
|
|
Prefix the expression with 'all' to allow any number of revisions (i.e. 'all:e|d').
|
2023-02-19 03:31:48 +00:00
|
|
|
"###);
|
2023-07-25 16:07:03 +00:00
|
|
|
let stdout = test_env.jj_cmd_success(&repo_path, &["rebase", "-b=all:e|d", "-d=b"]);
|
2023-02-19 03:31:48 +00:00
|
|
|
insta::assert_snapshot!(stdout, @r###"
|
|
|
|
Rebased 2 commits
|
|
|
|
Working copy now at: 817e3fb0dc64 e
|
2023-04-29 05:01:31 +00:00
|
|
|
Parent commit : 1394f625cbbd b
|
2023-02-19 03:31:48 +00:00
|
|
|
Added 1 files, modified 0 files, removed 0 files
|
|
|
|
"###);
|
|
|
|
insta::assert_snapshot!(get_log_output(&test_env, &repo_path), @r###"
|
2023-03-15 03:37:56 +00:00
|
|
|
◉ d
|
2023-02-19 03:31:48 +00:00
|
|
|
│ @ e
|
|
|
|
├─╯
|
2023-03-15 03:37:56 +00:00
|
|
|
│ ◉ c
|
2023-02-19 03:31:48 +00:00
|
|
|
├─╯
|
2023-03-15 03:37:56 +00:00
|
|
|
◉ b
|
|
|
|
◉ a
|
|
|
|
◉
|
2023-02-19 03:31:48 +00:00
|
|
|
"###);
|
2022-04-13 17:53:50 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
#[test]
|
|
|
|
fn test_rebase_branch_with_merge() {
|
|
|
|
let test_env = TestEnvironment::default();
|
|
|
|
test_env.jj_cmd_success(test_env.env_root(), &["init", "repo", "--git"]);
|
|
|
|
let repo_path = test_env.env_root().join("repo");
|
|
|
|
|
|
|
|
create_commit(&test_env, &repo_path, "a", &[]);
|
|
|
|
create_commit(&test_env, &repo_path, "b", &["a"]);
|
|
|
|
create_commit(&test_env, &repo_path, "c", &[]);
|
|
|
|
create_commit(&test_env, &repo_path, "d", &["c"]);
|
|
|
|
create_commit(&test_env, &repo_path, "e", &["a", "d"]);
|
|
|
|
// Test the setup
|
2022-05-29 23:46:47 +00:00
|
|
|
insta::assert_snapshot!(get_log_output(&test_env, &repo_path), @r###"
|
2023-02-09 02:53:47 +00:00
|
|
|
@ e
|
|
|
|
├─╮
|
2023-07-28 06:51:08 +00:00
|
|
|
│ ◉ d
|
|
|
|
│ ◉ c
|
2023-03-15 03:37:56 +00:00
|
|
|
│ │ ◉ b
|
2023-07-28 06:51:08 +00:00
|
|
|
├───╯
|
|
|
|
◉ │ a
|
2023-02-09 02:53:47 +00:00
|
|
|
├─╯
|
2023-03-15 03:37:56 +00:00
|
|
|
◉
|
2022-04-13 17:53:50 +00:00
|
|
|
"###);
|
|
|
|
|
|
|
|
let stdout = test_env.jj_cmd_success(&repo_path, &["rebase", "-b", "d", "-d", "b"]);
|
|
|
|
insta::assert_snapshot!(stdout, @r###"
|
2022-11-05 01:49:56 +00:00
|
|
|
Rebased 3 commits
|
2022-12-21 04:47:10 +00:00
|
|
|
Working copy now at: 391c91a7defa e
|
2023-04-29 05:01:31 +00:00
|
|
|
Parent commit : 1677f79555e4 d
|
2022-04-13 17:53:50 +00:00
|
|
|
Added 1 files, modified 0 files, removed 0 files
|
|
|
|
"###);
|
2022-05-29 23:46:47 +00:00
|
|
|
insta::assert_snapshot!(get_log_output(&test_env, &repo_path), @r###"
|
2023-02-09 02:53:47 +00:00
|
|
|
@ e
|
2023-03-15 03:37:56 +00:00
|
|
|
◉ d
|
|
|
|
◉ c
|
|
|
|
◉ b
|
|
|
|
◉ a
|
|
|
|
◉
|
2022-04-13 17:53:50 +00:00
|
|
|
"###);
|
|
|
|
|
|
|
|
test_env.jj_cmd_success(&repo_path, &["undo"]);
|
2022-04-14 06:53:35 +00:00
|
|
|
let stdout = test_env.jj_cmd_success(&repo_path, &["rebase", "-d", "b"]);
|
2022-04-13 17:53:50 +00:00
|
|
|
insta::assert_snapshot!(stdout, @r###"
|
2022-11-05 01:49:56 +00:00
|
|
|
Rebased 3 commits
|
2022-12-21 04:47:10 +00:00
|
|
|
Working copy now at: 040ae3a6d358 e
|
2023-04-29 05:01:31 +00:00
|
|
|
Parent commit : 3d0f3644db16 d
|
2022-04-13 17:53:50 +00:00
|
|
|
Added 1 files, modified 0 files, removed 0 files
|
|
|
|
"###);
|
2022-05-29 23:46:47 +00:00
|
|
|
insta::assert_snapshot!(get_log_output(&test_env, &repo_path), @r###"
|
2023-02-09 02:53:47 +00:00
|
|
|
@ e
|
2023-03-15 03:37:56 +00:00
|
|
|
◉ d
|
|
|
|
◉ c
|
|
|
|
◉ b
|
|
|
|
◉ a
|
|
|
|
◉
|
2022-04-13 17:53:50 +00:00
|
|
|
"###);
|
|
|
|
}
|
|
|
|
|
2022-04-13 13:43:54 +00:00
|
|
|
#[test]
|
|
|
|
fn test_rebase_single_revision() {
|
|
|
|
let test_env = TestEnvironment::default();
|
|
|
|
test_env.jj_cmd_success(test_env.env_root(), &["init", "repo", "--git"]);
|
|
|
|
let repo_path = test_env.env_root().join("repo");
|
|
|
|
|
|
|
|
create_commit(&test_env, &repo_path, "a", &[]);
|
|
|
|
create_commit(&test_env, &repo_path, "b", &[]);
|
|
|
|
create_commit(&test_env, &repo_path, "c", &["a", "b"]);
|
|
|
|
create_commit(&test_env, &repo_path, "d", &["c"]);
|
|
|
|
// Test the setup
|
2022-05-29 23:46:47 +00:00
|
|
|
insta::assert_snapshot!(get_log_output(&test_env, &repo_path), @r###"
|
2023-02-09 02:53:47 +00:00
|
|
|
@ d
|
2023-03-15 03:37:56 +00:00
|
|
|
◉ c
|
2023-02-09 02:53:47 +00:00
|
|
|
├─╮
|
2023-07-28 06:51:08 +00:00
|
|
|
│ ◉ b
|
|
|
|
◉ │ a
|
2023-02-09 02:53:47 +00:00
|
|
|
├─╯
|
2023-03-15 03:37:56 +00:00
|
|
|
◉
|
2022-04-13 13:43:54 +00:00
|
|
|
"###);
|
|
|
|
|
Fix `rebase -r` of a parent of a merge commit
Previously, using `rebase -r` on the parent of a merge commit
turned it into a non-merge commit. In other words, starting
with
```
o d
|\
o | c
o | b
| o a
|/
o
```
and doing `rebase -r c -d a` resulted in
```
o d
o b
| o c
| o a
|/
o
```
where `d` is no longer a merge commit.
For reference, here's a complete test that passed before this commit (but should NOT pass; see the diff for a test that should pass):
```
#[test]
fn test_rebase_single_revision_merge_parent() {
let test_env = TestEnvironment::default();
test_env.jj_cmd_success(test_env.env_root(), &["init", "repo", "--git"]);
let repo_path = test_env.env_root().join("repo");
create_commit(&test_env, &repo_path, "a", &[]);
create_commit(&test_env, &repo_path, "b", &[]);
create_commit(&test_env, &repo_path, "c", &["b"]);
create_commit(&test_env, &repo_path, "d", &["a", "c"]);
// Test the setup
insta::assert_snapshot!(get_log_output(&test_env, &repo_path), @r###"
@
o d
|\
o | c
o | b
| o a
|/
o
"###);
let stdout = test_env.jj_cmd_success(&repo_path, &["rebase", "-r", "c", "-d", "a"]);
insta::assert_snapshot!(stdout, @r###"
Also rebased 2 descendant commits onto parent of rebased commit
Working copy now at: 3e176b54d680 (no description set)
Added 0 files, modified 0 files, removed 2 files
"###);
insta::assert_snapshot!(get_log_output(&test_env, &repo_path), @r###"
@
o d
| o c
o | b
| o a
|/
o
"###);
}
```
2022-09-11 21:23:46 +00:00
|
|
|
// Descendants of the rebased commit "b" should be rebased onto parents. First
|
|
|
|
// we test with a non-merge commit. Normally, the descendant "c" would still
|
|
|
|
// have 2 parents afterwards: the parent of "b" -- the root commit -- and
|
|
|
|
// "a". However, since the root commit is an ancestor of "a", we don't
|
|
|
|
// actually want both to be parents of the same commit. So, only "a" becomes
|
|
|
|
// a parent.
|
2022-04-13 17:53:50 +00:00
|
|
|
let stdout = test_env.jj_cmd_success(&repo_path, &["rebase", "-r", "b", "-d", "a"]);
|
|
|
|
insta::assert_snapshot!(stdout, @r###"
|
2022-11-05 01:49:56 +00:00
|
|
|
Also rebased 2 descendant commits onto parent of rebased commit
|
2022-12-21 04:47:10 +00:00
|
|
|
Working copy now at: 7e15b97a447f d
|
2023-04-29 05:01:31 +00:00
|
|
|
Parent commit : 934236c8090e c
|
Fix `rebase -r` of a parent of a merge commit
Previously, using `rebase -r` on the parent of a merge commit
turned it into a non-merge commit. In other words, starting
with
```
o d
|\
o | c
o | b
| o a
|/
o
```
and doing `rebase -r c -d a` resulted in
```
o d
o b
| o c
| o a
|/
o
```
where `d` is no longer a merge commit.
For reference, here's a complete test that passed before this commit (but should NOT pass; see the diff for a test that should pass):
```
#[test]
fn test_rebase_single_revision_merge_parent() {
let test_env = TestEnvironment::default();
test_env.jj_cmd_success(test_env.env_root(), &["init", "repo", "--git"]);
let repo_path = test_env.env_root().join("repo");
create_commit(&test_env, &repo_path, "a", &[]);
create_commit(&test_env, &repo_path, "b", &[]);
create_commit(&test_env, &repo_path, "c", &["b"]);
create_commit(&test_env, &repo_path, "d", &["a", "c"]);
// Test the setup
insta::assert_snapshot!(get_log_output(&test_env, &repo_path), @r###"
@
o d
|\
o | c
o | b
| o a
|/
o
"###);
let stdout = test_env.jj_cmd_success(&repo_path, &["rebase", "-r", "c", "-d", "a"]);
insta::assert_snapshot!(stdout, @r###"
Also rebased 2 descendant commits onto parent of rebased commit
Working copy now at: 3e176b54d680 (no description set)
Added 0 files, modified 0 files, removed 2 files
"###);
insta::assert_snapshot!(get_log_output(&test_env, &repo_path), @r###"
@
o d
| o c
o | b
| o a
|/
o
"###);
}
```
2022-09-11 21:23:46 +00:00
|
|
|
Added 0 files, modified 0 files, removed 1 files
|
2022-04-13 17:53:50 +00:00
|
|
|
"###);
|
2022-05-29 23:46:47 +00:00
|
|
|
insta::assert_snapshot!(get_log_output(&test_env, &repo_path), @r###"
|
2023-02-09 02:53:47 +00:00
|
|
|
@ d
|
2023-03-15 03:37:56 +00:00
|
|
|
◉ c
|
|
|
|
│ ◉ b
|
2023-02-09 02:53:47 +00:00
|
|
|
├─╯
|
2023-03-15 03:37:56 +00:00
|
|
|
◉ a
|
|
|
|
◉
|
2022-04-13 13:43:54 +00:00
|
|
|
"###);
|
|
|
|
test_env.jj_cmd_success(&repo_path, &["undo"]);
|
Fix `rebase -r` of a parent of a merge commit
Previously, using `rebase -r` on the parent of a merge commit
turned it into a non-merge commit. In other words, starting
with
```
o d
|\
o | c
o | b
| o a
|/
o
```
and doing `rebase -r c -d a` resulted in
```
o d
o b
| o c
| o a
|/
o
```
where `d` is no longer a merge commit.
For reference, here's a complete test that passed before this commit (but should NOT pass; see the diff for a test that should pass):
```
#[test]
fn test_rebase_single_revision_merge_parent() {
let test_env = TestEnvironment::default();
test_env.jj_cmd_success(test_env.env_root(), &["init", "repo", "--git"]);
let repo_path = test_env.env_root().join("repo");
create_commit(&test_env, &repo_path, "a", &[]);
create_commit(&test_env, &repo_path, "b", &[]);
create_commit(&test_env, &repo_path, "c", &["b"]);
create_commit(&test_env, &repo_path, "d", &["a", "c"]);
// Test the setup
insta::assert_snapshot!(get_log_output(&test_env, &repo_path), @r###"
@
o d
|\
o | c
o | b
| o a
|/
o
"###);
let stdout = test_env.jj_cmd_success(&repo_path, &["rebase", "-r", "c", "-d", "a"]);
insta::assert_snapshot!(stdout, @r###"
Also rebased 2 descendant commits onto parent of rebased commit
Working copy now at: 3e176b54d680 (no description set)
Added 0 files, modified 0 files, removed 2 files
"###);
insta::assert_snapshot!(get_log_output(&test_env, &repo_path), @r###"
@
o d
| o c
o | b
| o a
|/
o
"###);
}
```
2022-09-11 21:23:46 +00:00
|
|
|
|
|
|
|
// Now, let's try moving the merge commit. After, both parents of "c" ("a" and
|
|
|
|
// "b") should become parents of "d".
|
2022-04-13 17:53:50 +00:00
|
|
|
let stdout = test_env.jj_cmd_success(&repo_path, &["rebase", "-r", "c", "-d", "root"]);
|
|
|
|
insta::assert_snapshot!(stdout, @r###"
|
2022-11-05 01:49:56 +00:00
|
|
|
Also rebased 1 descendant commits onto parent of rebased commit
|
2022-12-21 04:47:10 +00:00
|
|
|
Working copy now at: bf87078f4560 d
|
2023-04-29 05:01:31 +00:00
|
|
|
Parent commit : d370aee184ba b
|
|
|
|
Parent commit : 2443ea76b0b1 a
|
2022-04-13 17:53:50 +00:00
|
|
|
Added 0 files, modified 0 files, removed 1 files
|
|
|
|
"###);
|
2022-05-29 23:46:47 +00:00
|
|
|
insta::assert_snapshot!(get_log_output(&test_env, &repo_path), @r###"
|
2023-02-09 02:53:47 +00:00
|
|
|
@ d
|
|
|
|
├─╮
|
2023-03-15 03:37:56 +00:00
|
|
|
│ ◉ a
|
revset_graph: group commits topologically
The original idea was similar to Mercurial's "topo" sorting, but it was bad
at handling merge-heavy history. In order to render merges of topic branches
nicely, we need to prioritize branches at merge point, not at fork point.
OTOH, we do also want to place unmerged branches as close to the fork point
as possible. This commit implements the former requirement, and the latter
will be addressed by the next commit.
I think this is similar to Git's sorting logic described in the following blog
post. In our case, the in-degree walk can be dumb since topological order is
guaranteed by the index. We keep HashSet<CommitId> instead of an in-degree
integer value, which will be used in the next commit to resolve new heads as
late as possible.
https://github.blog/2022-08-30-gits-database-internals-ii-commit-history-queries/#topological-sorting
Compared to Sapling's beautify_graph(), this is lazy, and can roughly preserve
the index (or chronological) order. I tried beautify_graph() with prioritizing
the @ commit, but the result seemed too aggressively reordered. Perhaps, for
more complex history, beautify_graph() would produce a better result. For my
wip branches (~30 branches, a couple of commits per branch), this works pretty
well.
#242
2023-07-16 10:47:46 +00:00
|
|
|
◉ │ b
|
|
|
|
├─╯
|
|
|
|
│ ◉ c
|
2023-02-09 02:53:47 +00:00
|
|
|
├─╯
|
2023-03-15 03:37:56 +00:00
|
|
|
◉
|
2022-04-13 13:43:54 +00:00
|
|
|
"###);
|
|
|
|
}
|
|
|
|
|
Fix `rebase -r` of a parent of a merge commit
Previously, using `rebase -r` on the parent of a merge commit
turned it into a non-merge commit. In other words, starting
with
```
o d
|\
o | c
o | b
| o a
|/
o
```
and doing `rebase -r c -d a` resulted in
```
o d
o b
| o c
| o a
|/
o
```
where `d` is no longer a merge commit.
For reference, here's a complete test that passed before this commit (but should NOT pass; see the diff for a test that should pass):
```
#[test]
fn test_rebase_single_revision_merge_parent() {
let test_env = TestEnvironment::default();
test_env.jj_cmd_success(test_env.env_root(), &["init", "repo", "--git"]);
let repo_path = test_env.env_root().join("repo");
create_commit(&test_env, &repo_path, "a", &[]);
create_commit(&test_env, &repo_path, "b", &[]);
create_commit(&test_env, &repo_path, "c", &["b"]);
create_commit(&test_env, &repo_path, "d", &["a", "c"]);
// Test the setup
insta::assert_snapshot!(get_log_output(&test_env, &repo_path), @r###"
@
o d
|\
o | c
o | b
| o a
|/
o
"###);
let stdout = test_env.jj_cmd_success(&repo_path, &["rebase", "-r", "c", "-d", "a"]);
insta::assert_snapshot!(stdout, @r###"
Also rebased 2 descendant commits onto parent of rebased commit
Working copy now at: 3e176b54d680 (no description set)
Added 0 files, modified 0 files, removed 2 files
"###);
insta::assert_snapshot!(get_log_output(&test_env, &repo_path), @r###"
@
o d
| o c
o | b
| o a
|/
o
"###);
}
```
2022-09-11 21:23:46 +00:00
|
|
|
#[test]
|
|
|
|
fn test_rebase_single_revision_merge_parent() {
|
|
|
|
let test_env = TestEnvironment::default();
|
|
|
|
test_env.jj_cmd_success(test_env.env_root(), &["init", "repo", "--git"]);
|
|
|
|
let repo_path = test_env.env_root().join("repo");
|
|
|
|
|
|
|
|
create_commit(&test_env, &repo_path, "a", &[]);
|
|
|
|
create_commit(&test_env, &repo_path, "b", &[]);
|
|
|
|
create_commit(&test_env, &repo_path, "c", &["b"]);
|
|
|
|
create_commit(&test_env, &repo_path, "d", &["a", "c"]);
|
|
|
|
// Test the setup
|
|
|
|
insta::assert_snapshot!(get_log_output(&test_env, &repo_path), @r###"
|
2023-02-09 02:53:47 +00:00
|
|
|
@ d
|
|
|
|
├─╮
|
2023-07-28 06:51:08 +00:00
|
|
|
│ ◉ c
|
|
|
|
│ ◉ b
|
|
|
|
◉ │ a
|
2023-02-09 02:53:47 +00:00
|
|
|
├─╯
|
2023-03-15 03:37:56 +00:00
|
|
|
◉
|
Fix `rebase -r` of a parent of a merge commit
Previously, using `rebase -r` on the parent of a merge commit
turned it into a non-merge commit. In other words, starting
with
```
o d
|\
o | c
o | b
| o a
|/
o
```
and doing `rebase -r c -d a` resulted in
```
o d
o b
| o c
| o a
|/
o
```
where `d` is no longer a merge commit.
For reference, here's a complete test that passed before this commit (but should NOT pass; see the diff for a test that should pass):
```
#[test]
fn test_rebase_single_revision_merge_parent() {
let test_env = TestEnvironment::default();
test_env.jj_cmd_success(test_env.env_root(), &["init", "repo", "--git"]);
let repo_path = test_env.env_root().join("repo");
create_commit(&test_env, &repo_path, "a", &[]);
create_commit(&test_env, &repo_path, "b", &[]);
create_commit(&test_env, &repo_path, "c", &["b"]);
create_commit(&test_env, &repo_path, "d", &["a", "c"]);
// Test the setup
insta::assert_snapshot!(get_log_output(&test_env, &repo_path), @r###"
@
o d
|\
o | c
o | b
| o a
|/
o
"###);
let stdout = test_env.jj_cmd_success(&repo_path, &["rebase", "-r", "c", "-d", "a"]);
insta::assert_snapshot!(stdout, @r###"
Also rebased 2 descendant commits onto parent of rebased commit
Working copy now at: 3e176b54d680 (no description set)
Added 0 files, modified 0 files, removed 2 files
"###);
insta::assert_snapshot!(get_log_output(&test_env, &repo_path), @r###"
@
o d
| o c
o | b
| o a
|/
o
"###);
}
```
2022-09-11 21:23:46 +00:00
|
|
|
"###);
|
|
|
|
|
|
|
|
// Descendants of the rebased commit should be rebased onto parents, and if
|
|
|
|
// the descendant is a merge commit, it shouldn't forget its other parents.
|
|
|
|
let stdout = test_env.jj_cmd_success(&repo_path, &["rebase", "-r", "c", "-d", "a"]);
|
|
|
|
insta::assert_snapshot!(stdout, @r###"
|
2022-11-05 01:49:56 +00:00
|
|
|
Also rebased 1 descendant commits onto parent of rebased commit
|
2022-12-21 04:47:10 +00:00
|
|
|
Working copy now at: c62d0789e7c7 d
|
2023-04-29 05:01:31 +00:00
|
|
|
Parent commit : d370aee184ba b
|
|
|
|
Parent commit : 2443ea76b0b1 a
|
Fix `rebase -r` of a parent of a merge commit
Previously, using `rebase -r` on the parent of a merge commit
turned it into a non-merge commit. In other words, starting
with
```
o d
|\
o | c
o | b
| o a
|/
o
```
and doing `rebase -r c -d a` resulted in
```
o d
o b
| o c
| o a
|/
o
```
where `d` is no longer a merge commit.
For reference, here's a complete test that passed before this commit (but should NOT pass; see the diff for a test that should pass):
```
#[test]
fn test_rebase_single_revision_merge_parent() {
let test_env = TestEnvironment::default();
test_env.jj_cmd_success(test_env.env_root(), &["init", "repo", "--git"]);
let repo_path = test_env.env_root().join("repo");
create_commit(&test_env, &repo_path, "a", &[]);
create_commit(&test_env, &repo_path, "b", &[]);
create_commit(&test_env, &repo_path, "c", &["b"]);
create_commit(&test_env, &repo_path, "d", &["a", "c"]);
// Test the setup
insta::assert_snapshot!(get_log_output(&test_env, &repo_path), @r###"
@
o d
|\
o | c
o | b
| o a
|/
o
"###);
let stdout = test_env.jj_cmd_success(&repo_path, &["rebase", "-r", "c", "-d", "a"]);
insta::assert_snapshot!(stdout, @r###"
Also rebased 2 descendant commits onto parent of rebased commit
Working copy now at: 3e176b54d680 (no description set)
Added 0 files, modified 0 files, removed 2 files
"###);
insta::assert_snapshot!(get_log_output(&test_env, &repo_path), @r###"
@
o d
| o c
o | b
| o a
|/
o
"###);
}
```
2022-09-11 21:23:46 +00:00
|
|
|
Added 0 files, modified 0 files, removed 1 files
|
|
|
|
"###);
|
|
|
|
insta::assert_snapshot!(get_log_output(&test_env, &repo_path), @r###"
|
2023-02-09 02:53:47 +00:00
|
|
|
@ d
|
|
|
|
├─╮
|
revset_graph: group commits topologically
The original idea was similar to Mercurial's "topo" sorting, but it was bad
at handling merge-heavy history. In order to render merges of topic branches
nicely, we need to prioritize branches at merge point, not at fork point.
OTOH, we do also want to place unmerged branches as close to the fork point
as possible. This commit implements the former requirement, and the latter
will be addressed by the next commit.
I think this is similar to Git's sorting logic described in the following blog
post. In our case, the in-degree walk can be dumb since topological order is
guaranteed by the index. We keep HashSet<CommitId> instead of an in-degree
integer value, which will be used in the next commit to resolve new heads as
late as possible.
https://github.blog/2022-08-30-gits-database-internals-ii-commit-history-queries/#topological-sorting
Compared to Sapling's beautify_graph(), this is lazy, and can roughly preserve
the index (or chronological) order. I tried beautify_graph() with prioritizing
the @ commit, but the result seemed too aggressively reordered. Perhaps, for
more complex history, beautify_graph() would produce a better result. For my
wip branches (~30 branches, a couple of commits per branch), this works pretty
well.
#242
2023-07-16 10:47:46 +00:00
|
|
|
◉ │ b
|
2023-03-15 03:37:56 +00:00
|
|
|
│ │ ◉ c
|
2023-02-09 02:53:47 +00:00
|
|
|
│ ├─╯
|
2023-03-15 03:37:56 +00:00
|
|
|
│ ◉ a
|
2023-02-09 02:53:47 +00:00
|
|
|
├─╯
|
2023-03-15 03:37:56 +00:00
|
|
|
◉
|
Fix `rebase -r` of a parent of a merge commit
Previously, using `rebase -r` on the parent of a merge commit
turned it into a non-merge commit. In other words, starting
with
```
o d
|\
o | c
o | b
| o a
|/
o
```
and doing `rebase -r c -d a` resulted in
```
o d
o b
| o c
| o a
|/
o
```
where `d` is no longer a merge commit.
For reference, here's a complete test that passed before this commit (but should NOT pass; see the diff for a test that should pass):
```
#[test]
fn test_rebase_single_revision_merge_parent() {
let test_env = TestEnvironment::default();
test_env.jj_cmd_success(test_env.env_root(), &["init", "repo", "--git"]);
let repo_path = test_env.env_root().join("repo");
create_commit(&test_env, &repo_path, "a", &[]);
create_commit(&test_env, &repo_path, "b", &[]);
create_commit(&test_env, &repo_path, "c", &["b"]);
create_commit(&test_env, &repo_path, "d", &["a", "c"]);
// Test the setup
insta::assert_snapshot!(get_log_output(&test_env, &repo_path), @r###"
@
o d
|\
o | c
o | b
| o a
|/
o
"###);
let stdout = test_env.jj_cmd_success(&repo_path, &["rebase", "-r", "c", "-d", "a"]);
insta::assert_snapshot!(stdout, @r###"
Also rebased 2 descendant commits onto parent of rebased commit
Working copy now at: 3e176b54d680 (no description set)
Added 0 files, modified 0 files, removed 2 files
"###);
insta::assert_snapshot!(get_log_output(&test_env, &repo_path), @r###"
@
o d
| o c
o | b
| o a
|/
o
"###);
}
```
2022-09-11 21:23:46 +00:00
|
|
|
"###);
|
|
|
|
}
|
|
|
|
|
2022-04-13 13:43:54 +00:00
|
|
|
#[test]
|
|
|
|
fn test_rebase_multiple_destinations() {
|
|
|
|
let test_env = TestEnvironment::default();
|
|
|
|
test_env.jj_cmd_success(test_env.env_root(), &["init", "repo", "--git"]);
|
|
|
|
let repo_path = test_env.env_root().join("repo");
|
|
|
|
|
|
|
|
create_commit(&test_env, &repo_path, "a", &[]);
|
|
|
|
create_commit(&test_env, &repo_path, "b", &[]);
|
|
|
|
create_commit(&test_env, &repo_path, "c", &[]);
|
|
|
|
// Test the setup
|
2022-05-29 23:46:47 +00:00
|
|
|
insta::assert_snapshot!(get_log_output(&test_env, &repo_path), @r###"
|
2023-02-09 02:53:47 +00:00
|
|
|
@ c
|
2023-03-15 03:37:56 +00:00
|
|
|
│ ◉ b
|
2023-02-09 02:53:47 +00:00
|
|
|
├─╯
|
2023-03-15 03:37:56 +00:00
|
|
|
│ ◉ a
|
2023-02-09 02:53:47 +00:00
|
|
|
├─╯
|
2023-03-15 03:37:56 +00:00
|
|
|
◉
|
2022-04-13 13:43:54 +00:00
|
|
|
"###);
|
|
|
|
|
2022-04-13 17:53:50 +00:00
|
|
|
let stdout = test_env.jj_cmd_success(&repo_path, &["rebase", "-r", "a", "-d", "b", "-d", "c"]);
|
|
|
|
insta::assert_snapshot!(stdout, @r###""###);
|
2022-05-29 23:46:47 +00:00
|
|
|
insta::assert_snapshot!(get_log_output(&test_env, &repo_path), @r###"
|
2023-03-15 03:37:56 +00:00
|
|
|
◉ a
|
2023-02-09 02:53:47 +00:00
|
|
|
├─╮
|
2023-07-28 06:51:08 +00:00
|
|
|
│ @ c
|
|
|
|
◉ │ b
|
2023-02-09 02:53:47 +00:00
|
|
|
├─╯
|
2023-03-15 03:37:56 +00:00
|
|
|
◉
|
2022-04-13 13:43:54 +00:00
|
|
|
"###);
|
2022-09-12 09:45:16 +00:00
|
|
|
|
2023-02-04 08:24:48 +00:00
|
|
|
let stderr = test_env.jj_cmd_failure(&repo_path, &["rebase", "-r", "a", "-d", "b|c"]);
|
|
|
|
insta::assert_snapshot!(stderr, @r###"
|
|
|
|
Error: Revset "b|c" resolved to more than one revision
|
|
|
|
Hint: The revset "b|c" resolved to these revisions:
|
|
|
|
fe2e8e8b50b3 c
|
|
|
|
d370aee184ba b
|
2023-07-25 16:07:03 +00:00
|
|
|
Prefix the expression with 'all' to allow any number of revisions (i.e. 'all:b|c').
|
2023-02-04 08:24:48 +00:00
|
|
|
"###);
|
2023-07-25 16:07:03 +00:00
|
|
|
let stdout = test_env.jj_cmd_success(&repo_path, &["rebase", "-r", "a", "-d", "all:b|c"]);
|
2023-01-31 06:32:18 +00:00
|
|
|
insta::assert_snapshot!(stdout, @r###""###);
|
|
|
|
insta::assert_snapshot!(get_log_output(&test_env, &repo_path), @r###"
|
2023-03-15 03:37:56 +00:00
|
|
|
◉ a
|
2023-02-09 02:53:47 +00:00
|
|
|
├─╮
|
2023-03-15 03:37:56 +00:00
|
|
|
│ ◉ b
|
revset_graph: group commits topologically
The original idea was similar to Mercurial's "topo" sorting, but it was bad
at handling merge-heavy history. In order to render merges of topic branches
nicely, we need to prioritize branches at merge point, not at fork point.
OTOH, we do also want to place unmerged branches as close to the fork point
as possible. This commit implements the former requirement, and the latter
will be addressed by the next commit.
I think this is similar to Git's sorting logic described in the following blog
post. In our case, the in-degree walk can be dumb since topological order is
guaranteed by the index. We keep HashSet<CommitId> instead of an in-degree
integer value, which will be used in the next commit to resolve new heads as
late as possible.
https://github.blog/2022-08-30-gits-database-internals-ii-commit-history-queries/#topological-sorting
Compared to Sapling's beautify_graph(), this is lazy, and can roughly preserve
the index (or chronological) order. I tried beautify_graph() with prioritizing
the @ commit, but the result seemed too aggressively reordered. Perhaps, for
more complex history, beautify_graph() would produce a better result. For my
wip branches (~30 branches, a couple of commits per branch), this works pretty
well.
#242
2023-07-16 10:47:46 +00:00
|
|
|
@ │ c
|
2023-02-09 02:53:47 +00:00
|
|
|
├─╯
|
2023-03-15 03:37:56 +00:00
|
|
|
◉
|
2023-01-31 06:32:18 +00:00
|
|
|
"###);
|
2023-02-04 08:24:48 +00:00
|
|
|
|
|
|
|
let stderr = test_env.jj_cmd_failure(&repo_path, &["rebase", "-r", "a", "-d", "b", "-d", "b"]);
|
|
|
|
insta::assert_snapshot!(stderr, @r###"
|
2023-02-04 05:33:17 +00:00
|
|
|
Error: More than one revset resolved to revision d370aee184ba
|
2023-02-04 08:24:48 +00:00
|
|
|
"###);
|
|
|
|
|
2023-07-25 16:07:03 +00:00
|
|
|
// Same error with 'all:' if there is overlap.
|
2023-07-25 17:17:36 +00:00
|
|
|
let stderr = test_env.jj_cmd_failure(
|
2023-01-31 06:32:18 +00:00
|
|
|
&repo_path,
|
2023-07-25 16:07:03 +00:00
|
|
|
&["rebase", "-r", "a", "-d", "all:b|c", "-d", "b"],
|
2023-01-31 06:32:18 +00:00
|
|
|
);
|
2023-07-25 17:17:36 +00:00
|
|
|
insta::assert_snapshot!(stderr, @r###"
|
|
|
|
Error: More than one revset resolved to revision d370aee184ba
|
2023-01-31 06:32:18 +00:00
|
|
|
"###);
|
|
|
|
|
2022-11-18 20:50:39 +00:00
|
|
|
let stderr =
|
|
|
|
test_env.jj_cmd_failure(&repo_path, &["rebase", "-r", "a", "-d", "b", "-d", "root"]);
|
|
|
|
insta::assert_snapshot!(stderr, @r###"
|
|
|
|
Error: Cannot merge with root revision
|
|
|
|
"###);
|
2022-04-13 13:43:54 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
#[test]
|
|
|
|
fn test_rebase_with_descendants() {
|
|
|
|
let test_env = TestEnvironment::default();
|
|
|
|
test_env.jj_cmd_success(test_env.env_root(), &["init", "repo", "--git"]);
|
|
|
|
let repo_path = test_env.env_root().join("repo");
|
|
|
|
|
|
|
|
create_commit(&test_env, &repo_path, "a", &[]);
|
|
|
|
create_commit(&test_env, &repo_path, "b", &[]);
|
|
|
|
create_commit(&test_env, &repo_path, "c", &["a", "b"]);
|
|
|
|
create_commit(&test_env, &repo_path, "d", &["c"]);
|
|
|
|
// Test the setup
|
2022-05-29 23:46:47 +00:00
|
|
|
insta::assert_snapshot!(get_log_output(&test_env, &repo_path), @r###"
|
2023-02-09 02:53:47 +00:00
|
|
|
@ d
|
2023-03-15 03:37:56 +00:00
|
|
|
◉ c
|
2023-02-09 02:53:47 +00:00
|
|
|
├─╮
|
2023-07-28 06:51:08 +00:00
|
|
|
│ ◉ b
|
|
|
|
◉ │ a
|
2023-02-09 02:53:47 +00:00
|
|
|
├─╯
|
2023-03-15 03:37:56 +00:00
|
|
|
◉
|
2022-04-13 13:43:54 +00:00
|
|
|
"###);
|
|
|
|
|
2022-04-13 17:53:50 +00:00
|
|
|
let stdout = test_env.jj_cmd_success(&repo_path, &["rebase", "-s", "b", "-d", "a"]);
|
|
|
|
insta::assert_snapshot!(stdout, @r###"
|
2022-11-05 01:49:56 +00:00
|
|
|
Rebased 3 commits
|
2022-12-21 04:47:10 +00:00
|
|
|
Working copy now at: 309336ffce22 d
|
2023-04-29 05:01:31 +00:00
|
|
|
Parent commit : 244fa794aa18 c
|
2022-04-13 17:53:50 +00:00
|
|
|
"###);
|
2022-05-29 23:46:47 +00:00
|
|
|
insta::assert_snapshot!(get_log_output(&test_env, &repo_path), @r###"
|
2023-02-09 02:53:47 +00:00
|
|
|
@ d
|
2023-03-15 03:37:56 +00:00
|
|
|
◉ c
|
|
|
|
◉ b
|
|
|
|
◉ a
|
|
|
|
◉
|
2022-04-13 13:43:54 +00:00
|
|
|
"###);
|
2023-02-19 03:31:48 +00:00
|
|
|
|
|
|
|
// Rebase several subtrees at once.
|
|
|
|
test_env.jj_cmd_success(&repo_path, &["undo"]);
|
|
|
|
let stdout = test_env.jj_cmd_success(&repo_path, &["rebase", "-s=c", "-s=d", "-d=a"]);
|
|
|
|
insta::assert_snapshot!(stdout, @r###"
|
|
|
|
Rebased 2 commits
|
|
|
|
Working copy now at: 92c2bc9a8623 d
|
2023-04-29 05:01:31 +00:00
|
|
|
Parent commit : 2443ea76b0b1 a
|
2023-02-19 03:31:48 +00:00
|
|
|
Added 0 files, modified 0 files, removed 2 files
|
|
|
|
"###);
|
|
|
|
insta::assert_snapshot!(get_log_output(&test_env, &repo_path), @r###"
|
|
|
|
@ d
|
2023-03-15 03:37:56 +00:00
|
|
|
│ ◉ c
|
2023-02-19 03:31:48 +00:00
|
|
|
├─╯
|
revset_graph: group commits topologically
The original idea was similar to Mercurial's "topo" sorting, but it was bad
at handling merge-heavy history. In order to render merges of topic branches
nicely, we need to prioritize branches at merge point, not at fork point.
OTOH, we do also want to place unmerged branches as close to the fork point
as possible. This commit implements the former requirement, and the latter
will be addressed by the next commit.
I think this is similar to Git's sorting logic described in the following blog
post. In our case, the in-degree walk can be dumb since topological order is
guaranteed by the index. We keep HashSet<CommitId> instead of an in-degree
integer value, which will be used in the next commit to resolve new heads as
late as possible.
https://github.blog/2022-08-30-gits-database-internals-ii-commit-history-queries/#topological-sorting
Compared to Sapling's beautify_graph(), this is lazy, and can roughly preserve
the index (or chronological) order. I tried beautify_graph() with prioritizing
the @ commit, but the result seemed too aggressively reordered. Perhaps, for
more complex history, beautify_graph() would produce a better result. For my
wip branches (~30 branches, a couple of commits per branch), this works pretty
well.
#242
2023-07-16 10:47:46 +00:00
|
|
|
◉ a
|
2023-03-15 03:37:56 +00:00
|
|
|
│ ◉ b
|
2023-02-19 03:31:48 +00:00
|
|
|
├─╯
|
2023-03-15 03:37:56 +00:00
|
|
|
◉
|
2023-02-19 03:31:48 +00:00
|
|
|
"###);
|
|
|
|
|
|
|
|
test_env.jj_cmd_success(&repo_path, &["undo"]);
|
|
|
|
// Reminder of the setup
|
|
|
|
insta::assert_snapshot!(get_log_output(&test_env, &repo_path), @r###"
|
|
|
|
@ d
|
2023-03-15 03:37:56 +00:00
|
|
|
◉ c
|
2023-02-19 03:31:48 +00:00
|
|
|
├─╮
|
2023-07-28 06:51:08 +00:00
|
|
|
│ ◉ b
|
|
|
|
◉ │ a
|
2023-02-19 03:31:48 +00:00
|
|
|
├─╯
|
2023-03-15 03:37:56 +00:00
|
|
|
◉
|
2023-02-19 03:31:48 +00:00
|
|
|
"###);
|
|
|
|
|
|
|
|
// `d` was a descendant of `b`, and both are moved to be direct descendants of
|
|
|
|
// `a`. `c` remains a descendant of `b`.
|
|
|
|
let stdout = test_env.jj_cmd_success(&repo_path, &["rebase", "-s=b", "-s=d", "-d=a"]);
|
|
|
|
insta::assert_snapshot!(stdout, @r###"
|
|
|
|
Rebased 3 commits
|
|
|
|
Working copy now at: f1e71cb78a06 d
|
2023-04-29 05:01:31 +00:00
|
|
|
Parent commit : 2443ea76b0b1 a
|
2023-02-19 03:31:48 +00:00
|
|
|
Added 0 files, modified 0 files, removed 2 files
|
|
|
|
"###);
|
|
|
|
insta::assert_snapshot!(get_log_output(&test_env, &repo_path), @r###"
|
2023-03-15 03:37:56 +00:00
|
|
|
◉ c
|
revset_graph: group commits topologically
The original idea was similar to Mercurial's "topo" sorting, but it was bad
at handling merge-heavy history. In order to render merges of topic branches
nicely, we need to prioritize branches at merge point, not at fork point.
OTOH, we do also want to place unmerged branches as close to the fork point
as possible. This commit implements the former requirement, and the latter
will be addressed by the next commit.
I think this is similar to Git's sorting logic described in the following blog
post. In our case, the in-degree walk can be dumb since topological order is
guaranteed by the index. We keep HashSet<CommitId> instead of an in-degree
integer value, which will be used in the next commit to resolve new heads as
late as possible.
https://github.blog/2022-08-30-gits-database-internals-ii-commit-history-queries/#topological-sorting
Compared to Sapling's beautify_graph(), this is lazy, and can roughly preserve
the index (or chronological) order. I tried beautify_graph() with prioritizing
the @ commit, but the result seemed too aggressively reordered. Perhaps, for
more complex history, beautify_graph() would produce a better result. For my
wip branches (~30 branches, a couple of commits per branch), this works pretty
well.
#242
2023-07-16 10:47:46 +00:00
|
|
|
◉ b
|
2023-02-19 03:31:48 +00:00
|
|
|
│ @ d
|
|
|
|
├─╯
|
2023-03-15 03:37:56 +00:00
|
|
|
◉ a
|
|
|
|
◉
|
2023-02-19 03:31:48 +00:00
|
|
|
"###);
|
|
|
|
|
2023-07-25 17:17:36 +00:00
|
|
|
// Same test as above, but with multiple commits per argument
|
2023-02-19 03:31:48 +00:00
|
|
|
test_env.jj_cmd_success(&repo_path, &["undo"]);
|
2023-07-25 17:17:36 +00:00
|
|
|
let stderr = test_env.jj_cmd_failure(&repo_path, &["rebase", "-s=b|d", "-d=a"]);
|
2023-02-19 03:31:48 +00:00
|
|
|
insta::assert_snapshot!(stderr, @r###"
|
|
|
|
Error: Revset "b|d" resolved to more than one revision
|
|
|
|
Hint: The revset "b|d" resolved to these revisions:
|
|
|
|
df54a9fd85ae d
|
|
|
|
d370aee184ba b
|
2023-07-25 16:07:03 +00:00
|
|
|
Prefix the expression with 'all' to allow any number of revisions (i.e. 'all:b|d').
|
2023-02-19 03:31:48 +00:00
|
|
|
"###);
|
2023-07-25 16:07:03 +00:00
|
|
|
let stdout = test_env.jj_cmd_success(&repo_path, &["rebase", "-s=all:b|d", "-d=a"]);
|
2023-02-19 03:31:48 +00:00
|
|
|
insta::assert_snapshot!(stdout, @r###"
|
|
|
|
Rebased 3 commits
|
|
|
|
Working copy now at: d17539f7ea7c d
|
2023-04-29 05:01:31 +00:00
|
|
|
Parent commit : 2443ea76b0b1 a
|
2023-02-19 03:31:48 +00:00
|
|
|
Added 0 files, modified 0 files, removed 2 files
|
|
|
|
"###);
|
|
|
|
insta::assert_snapshot!(get_log_output(&test_env, &repo_path), @r###"
|
2023-03-15 03:37:56 +00:00
|
|
|
◉ c
|
|
|
|
◉ b
|
2023-02-19 03:31:48 +00:00
|
|
|
│ @ d
|
|
|
|
├─╯
|
2023-03-15 03:37:56 +00:00
|
|
|
◉ a
|
|
|
|
◉
|
2023-02-19 03:31:48 +00:00
|
|
|
"###);
|
2022-04-13 13:43:54 +00:00
|
|
|
}
|
2022-05-29 23:46:47 +00:00
|
|
|
|
|
|
|
fn get_log_output(test_env: &TestEnvironment, repo_path: &Path) -> String {
|
|
|
|
test_env.jj_cmd_success(repo_path, &["log", "-T", "branches"])
|
|
|
|
}
|