You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<baseCommitRev> Git revision of the commit that will be the base of the merge
15
-
<commitRev> Git revision of the commit that will be merged over the base
13
+
<path> Path to the git repository
14
+
<baseCommitRev> Git revision of the commit that will be the base of the merge
15
+
<targetCommitRev> Git revision of the commit that will be merged over the base
16
16
17
17
DESCRIPTION:
18
-
%_COMMAND_NAME_% Incorporates changes from the passed <commitRev> over <baseCommitRev> and moves the HEAD of the repo to the merge commit.
18
+
%_COMMAND_NAME_% Incorporates changes from the passed <targetCommitRev> over <baseCommitRev> and moves the HEAD of the repo to the merge commit.
19
19
20
20
OPTIONS:
21
21
If no options passed, the merge commit will be avoided if it could be considered as a fast-forward, and if needed, it will be used a default merge commit message.
@@ -32,16 +32,11 @@ OPTIONS:
32
32
[NOT IMPLEMENTED]
33
33
Create a merge commit even when the merge resolves as a fast-forward.
34
34
35
-
--no-commit
36
-
[NOT IMPLEMENTED]
37
-
With --no-commit perform the merge but pretend the merge failed and do not autocommit, to give the user a chance to
38
-
inspect and further tweak the merge result before committing.
39
-
40
35
--allow-unrelated-histories
41
36
[NOT IMPLEMENTED]
42
37
By default, git merge command refuses to merge histories that do not share a common ancestor. This option can be
43
38
used to override this safety when merging histories of two projects that started their lives independently.
44
-
39
+
45
40
DISCUSSION:
46
41
Assume the following history exists and the current branch is "master":
0 commit comments