@teambit/harmony.content.cli-reference 2.0.261 → 2.0.263

package/cli-reference.docs.mdx

@@ -1,5 +1,5 @@
 ---
-description: 'Bit command synopses. Bit version: 1.6.146'
+description: 'Bit command synopses. Bit version: 1.6.148'
 labels: ['cli', 'mdx', 'docs']
 ---
       

package/cli-reference.json

@@ -4086,6 +4086,20 @@
         "extendedDescription": "restore the lane-object to its state before the last \"bit lane merge\" command.\nalso, checkout the workspace components according to the restored lane state",
         "private": true,
         "remoteOp": true
+      },
+      {
+        "name": "merge-move <new-lane-name>",
+        "alias": "",
+        "options": [
+          [
+            "s",
+            "scope <scope-name>",
+            "remote scope to which this lane will be exported, default to the workspace.json's defaultScope (can be changed up to first export of the lane with \"bit lane change-scope\")"
+          ]
+        ],
+        "description": "EXPERIMENT. move the current merge state into a new lane. the current lane will be reset",
+        "extendedDescription": "this command is useful when you got a messy merge state that from one hand you don't want\nto loose the changes, but on the other hand, you want to keep your lane without those changes.\nthis command does the following:\n1. create a new lane with the current merge state. including all the filesystem changes. (in practice, it leaves the fs intact)\n2. reset the current lane to the state before the merge. so then once done with the new lane, you can switch to the current lane and it'll be clean.",
+        "remoteOp": true
       }
     ]
   },

package/cli-reference.mdx

@@ -1260,6 +1260,22 @@ also, checkout the workspace components according to the restored lane state
 | `--silent`                       |       `-s`       | skip confirmation                                        |
 | `--skip-dependency-installation` |       `-x`       | do not install packages of the imported components       |
 
+### lane merge-move
+
+**Usage**: `lane merge-move <new-lane-name>`
+
+**Description**: EXPERIMENT. move the current merge state into a new lane. the current lane will be reset  
+this command is useful when you got a messy merge state that from one hand you don't want  
+to loose the changes, but on the other hand, you want to keep your lane without those changes.  
+this command does the following:
+
+1. create a new lane with the current merge state. including all the filesystem changes. (in practice, it leaves the fs intact)
+2. reset the current lane to the state before the merge. so then once done with the new lane, you can switch to the current lane and it'll be clean.
+
+| **Option**             | **Option alias** | **Description**                                                                                                                                                             |
+| ---------------------- | :--------------: | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `--scope <scope-name>` |       `-s`       | remote scope to which this lane will be exported, default to the workspace.json's defaultScope (can be changed up to first export of the lane with "bit lane change-scope") |
+
 | **Option**                     | **Option alias** | **Description**                                               |
 | ------------------------------ | :--------------: | ------------------------------------------------------------- |
 | `--details`                    |       `-d`       | show more details on the state of each component in each lane |

package/dist/cli-reference.docs.mdx

@@ -1,5 +1,5 @@
 ---
-description: 'Bit command synopses. Bit version: 1.6.146'
+description: 'Bit command synopses. Bit version: 1.6.148'
 labels: ['cli', 'mdx', 'docs']
 ---
       

package/dist/cli-reference.json

@@ -4086,6 +4086,20 @@
                 "extendedDescription": "restore the lane-object to its state before the last \"bit lane merge\" command.\nalso, checkout the workspace components according to the restored lane state",
                 "private": true,
                 "remoteOp": true
+            },
+            {
+                "name": "merge-move <new-lane-name>",
+                "alias": "",
+                "options": [
+                    [
+                        "s",
+                        "scope <scope-name>",
+                        "remote scope to which this lane will be exported, default to the workspace.json's defaultScope (can be changed up to first export of the lane with \"bit lane change-scope\")"
+                    ]
+                ],
+                "description": "EXPERIMENT. move the current merge state into a new lane. the current lane will be reset",
+                "extendedDescription": "this command is useful when you got a messy merge state that from one hand you don't want\nto loose the changes, but on the other hand, you want to keep your lane without those changes.\nthis command does the following:\n1. create a new lane with the current merge state. including all the filesystem changes. (in practice, it leaves the fs intact)\n2. reset the current lane to the state before the merge. so then once done with the new lane, you can switch to the current lane and it'll be clean.",
+                "remoteOp": true
             }
         ]
     },

package/dist/cli-reference.mdx.js

@@ -6569,7 +6569,59 @@ function MDXContent(_ref) {
   }, "-x")), (0, _react2.mdx)("td", {
     parentName: "tr",
     "align": null
-  }, "do not install packages of the imported components")))), (0, _react2.mdx)("table", null, (0, _react2.mdx)("thead", {
+  }, "do not install packages of the imported components")))), (0, _react2.mdx)("h3", null, "lane merge-move"), (0, _react2.mdx)("p", null, (0, _react2.mdx)("strong", {
+    parentName: "p"
+  }, "Usage"), ": ", (0, _react2.mdx)("inlineCode", {
+    parentName: "p"
+  }, "lane merge-move <new-lane-name>")), (0, _react2.mdx)("p", null, (0, _react2.mdx)("strong", {
+    parentName: "p"
+  }, "Description"), ": EXPERIMENT. move the current merge state into a new lane. the current lane will be reset", (0, _react2.mdx)("br", {
+    parentName: "p"
+  }), "\n", "this command is useful when you got a messy merge state that from one hand you don't want", (0, _react2.mdx)("br", {
+    parentName: "p"
+  }), "\n", "to loose the changes, but on the other hand, you want to keep your lane without those changes.", (0, _react2.mdx)("br", {
+    parentName: "p"
+  }), "\n", "this command does the following:"), (0, _react2.mdx)("ol", null, (0, _react2.mdx)("li", {
+    parentName: "ol"
+  }, "create a new lane with the current merge state. including all the filesystem changes. (in practice, it leaves the fs intact)"), (0, _react2.mdx)("li", {
+    parentName: "ol"
+  }, "reset the current lane to the state before the merge. so then once done with the new lane, you can switch to the current lane and it'll be clean.")), (0, _react2.mdx)("table", null, (0, _react2.mdx)("thead", {
+    parentName: "table"
+  }, (0, _react2.mdx)("tr", {
+    parentName: "thead"
+  }, (0, _react2.mdx)("th", {
+    parentName: "tr",
+    "align": null
+  }, (0, _react2.mdx)("strong", {
+    parentName: "th"
+  }, "Option")), (0, _react2.mdx)("th", {
+    parentName: "tr",
+    "align": "center"
+  }, (0, _react2.mdx)("strong", {
+    parentName: "th"
+  }, "Option alias")), (0, _react2.mdx)("th", {
+    parentName: "tr",
+    "align": null
+  }, (0, _react2.mdx)("strong", {
+    parentName: "th"
+  }, "Description")))), (0, _react2.mdx)("tbody", {
+    parentName: "table"
+  }, (0, _react2.mdx)("tr", {
+    parentName: "tbody"
+  }, (0, _react2.mdx)("td", {
+    parentName: "tr",
+    "align": null
+  }, (0, _react2.mdx)("inlineCode", {
+    parentName: "td"
+  }, "--scope <scope-name>")), (0, _react2.mdx)("td", {
+    parentName: "tr",
+    "align": "center"
+  }, (0, _react2.mdx)("inlineCode", {
+    parentName: "td"
+  }, "-s")), (0, _react2.mdx)("td", {
+    parentName: "tr",
+    "align": null
+  }, "remote scope to which this lane will be exported, default to the workspace.json's defaultScope (can be changed up to first export of the lane with \"bit lane change-scope\")")))), (0, _react2.mdx)("table", null, (0, _react2.mdx)("thead", {
     parentName: "table"
   }, (0, _react2.mdx)("tr", {
     parentName: "thead"