@teambit/harmony.content.cli-reference 1.95.89 → 1.95.92

package/cli-reference.json

@@ -1213,6 +1213,11 @@
         "all",
         "all components"
       ],
+      [
+        "e",
+        "entire-lane",
+        "write also new components that were introduced on the remote lane and do not exist locally"
+      ],
       [
         "v",
         "verbose",
@@ -2066,9 +2071,9 @@
         "EXPERIMENTAL. complete a merge process by snapping the unmerged components"
       ],
       [
-        "",
+        "b",
         "build",
-        "Harmony only. run the pipeline build and complete the tag"
+        "EXPERIMENTAL. not needed for now. run the build pipeline in case the feature-flag build-on-ci is enabled"
       ],
       [
         "",
@@ -2088,7 +2093,7 @@
       [
         "",
         "force-deploy",
-        "Harmony only. run the deploy pipeline although the build failed"
+        "run the deploy pipeline although the build failed"
       ],
       [
         "i",
@@ -2237,12 +2242,57 @@
         "ignore existing of newer versions (default = false)"
       ]
     ],
-    "description": "create an immutable and exportable component snapshot, tagged with a release version.",
-    "extendedDescription": "this command should be running from a new bare scope, it first imports the components it needs and then processes the tag.\nthe input data is a stringified JSON of an array of the following object.\n{\n  componentId: string;    // ids always have scope, so it's safe to parse them from string\n  dependencies: string[]; // e.g. [teambit/compiler@1.0.0, teambit/tester@1.0.0]\n  versionToTag?: string;  // specific version (e.g. '1.0.0') or semver (e.g. 'minor', 'patch')\n  prereleaseId?: string;  // applicable when versionToTag is a pre-release. (e.g. \"dev\", for 1.0.0-dev.1)\n  message?: string;       // tag-message.\n}\nan example of the final data: '[{\"componentId\":\"ci.remote2/comp-b\",\"dependencies\":[\"ci.remote/comp1@0.0.2\"]}]'\n",
+    "description": "tag components from a bare-scope by using build artifacts from previous snap and running the deploy-pipeline only",
+    "extendedDescription": "this command should be running from a new bare scope, it first imports the components it needs and then processes the tag.\nthe input data is a stringified JSON of an array of the following object.\n{\n  componentId: string;    // ids always have scope, so it's safe to parse them from string\n  dependencies?: string[]; // e.g. [teambit/compiler@1.0.0, teambit/tester@1.0.0]\n  versionToTag?: string;  // specific version (e.g. '1.0.0') or semver (e.g. 'minor', 'patch')\n  prereleaseId?: string;  // applicable when versionToTag is a pre-release. (e.g. \"dev\", for 1.0.0-dev.1)\n  message?: string;       // tag-message.\n}\nan example of the final data: '[{\"componentId\":\"ci.remote2/comp-b\",\"dependencies\":[\"ci.remote/comp1@0.0.2\"]}]'\n",
     "group": "development",
     "private": true,
     "remoteOp": true
   },
+  {
+    "name": "_snap <data>",
+    "alias": "",
+    "options": [
+      [
+        "",
+        "push",
+        "export the updated objects to the original scopes once done"
+      ],
+      [
+        "m",
+        "message <message>",
+        "log message describing the latest changes"
+      ],
+      [
+        "",
+        "build",
+        "run the build pipeline"
+      ],
+      [
+        "",
+        "skip-tests",
+        "skip running component tests during snap process"
+      ],
+      [
+        "",
+        "disable-snap-pipeline",
+        "skip the snap pipeline"
+      ],
+      [
+        "",
+        "force-deploy",
+        "run the deploy pipeline although the build failed"
+      ],
+      [
+        "i",
+        "ignore-issues [issues]",
+        "ignore component issues (shown in \"bit status\" as \"issues found\"), issues to ignore:\n[MissingPackagesDependenciesOnFs, MissingComponents, UntrackedDependencies, ResolveErrors, RelativeComponents, RelativeComponentsAuthored, ParseErrors, MissingDists, LegacyInsideHarmony, MissingDependenciesOnFs, ImportNonMainFiles, CustomModuleResolutionUsed, MultipleEnvs, MissingLinksFromNodeModulesToSrc, CircularDependencies, DuplicateComponentAndPackage]\nto ignore multiple issues, separate them by a comma and wrap with quotes. to ignore all issues, specify \"*\"."
+      ]
+    ],
+    "description": "snap components from a bare-scope",
+    "extendedDescription": "this command should be running from a new bare scope, it first imports the components it needs and then processes the snap.\nthe input data is a stringified JSON of an array of the following object.\n{\n  componentId: string;    // ids always have scope, so it's safe to parse them from string\n  dependencies?: string[]; // e.g. [teambit/compiler@1.0.0, teambit/tester@1.0.0]\n  aspects?: Record<string,any> // e.g. { \"teambit.react/react\": {}, \"teambit.envs/envs\": { \"env\": \"teambit.react/react\" } }\n  message?: string;       // tag-message.\n}\nan example of the final data: '[{\"componentId\":\"ci.remote2/comp-b\",\"message\": \"first snap\"}]'\n",
+    "group": "ungrouped",
+    "private": true
+  },
   {
     "name": "merge [values...]",
     "alias": "",
@@ -2746,6 +2796,11 @@
         "",
         "include-deps",
         "EXPERIMENTAL. relevant for \"--pattern\". merge also dependencies of the given components"
+      ],
+      [
+        "j",
+        "json",
+        "output as json format"
       ]
     ],
     "description": "merge a remote lane into main via a bare-scope (not workspace)",

package/cli-reference.mdx

@@ -233,6 +233,7 @@ with no args, only workspace's capsules are deleted
 | `--manual`                       |       `-m`       | in case of a conflict, leave the files with a conflict state to resolve them manually later         |
 | `--reset`                        |       `-r`       | revert changes that were not snapped/tagged                                                         |
 | `--all`                          |       `-a`       | all components                                                                                      |
+| `--entire-lane`                  |       `-e`       | write also new components that were introduced on the remote lane and do not exist locally          |
 | `--verbose`                      |       `-v`       | showing verbose output for inspection                                                               |
 | `--reset`                        |                  | DEPRECATED. run "bit checkout reset" instead                                                        |
 | `--skip-npm-install`             |                  | DEPRECATED. use "--skip-dependency-installation" instead                                            |

package/dist/cli-reference.json

@@ -1213,6 +1213,11 @@
                 "all",
                 "all components"
             ],
+            [
+                "e",
+                "entire-lane",
+                "write also new components that were introduced on the remote lane and do not exist locally"
+            ],
             [
                 "v",
                 "verbose",
@@ -2066,9 +2071,9 @@
                 "EXPERIMENTAL. complete a merge process by snapping the unmerged components"
             ],
             [
-                "",
+                "b",
                 "build",
-                "Harmony only. run the pipeline build and complete the tag"
+                "EXPERIMENTAL. not needed for now. run the build pipeline in case the feature-flag build-on-ci is enabled"
             ],
             [
                 "",
@@ -2088,7 +2093,7 @@
             [
                 "",
                 "force-deploy",
-                "Harmony only. run the deploy pipeline although the build failed"
+                "run the deploy pipeline although the build failed"
             ],
             [
                 "i",
@@ -2237,12 +2242,57 @@
                 "ignore existing of newer versions (default = false)"
             ]
         ],
-        "description": "create an immutable and exportable component snapshot, tagged with a release version.",
-        "extendedDescription": "this command should be running from a new bare scope, it first imports the components it needs and then processes the tag.\nthe input data is a stringified JSON of an array of the following object.\n{\n  componentId: string;    // ids always have scope, so it's safe to parse them from string\n  dependencies: string[]; // e.g. [teambit/compiler@1.0.0, teambit/tester@1.0.0]\n  versionToTag?: string;  // specific version (e.g. '1.0.0') or semver (e.g. 'minor', 'patch')\n  prereleaseId?: string;  // applicable when versionToTag is a pre-release. (e.g. \"dev\", for 1.0.0-dev.1)\n  message?: string;       // tag-message.\n}\nan example of the final data: '[{\"componentId\":\"ci.remote2/comp-b\",\"dependencies\":[\"ci.remote/comp1@0.0.2\"]}]'\n",
+        "description": "tag components from a bare-scope by using build artifacts from previous snap and running the deploy-pipeline only",
+        "extendedDescription": "this command should be running from a new bare scope, it first imports the components it needs and then processes the tag.\nthe input data is a stringified JSON of an array of the following object.\n{\n  componentId: string;    // ids always have scope, so it's safe to parse them from string\n  dependencies?: string[]; // e.g. [teambit/compiler@1.0.0, teambit/tester@1.0.0]\n  versionToTag?: string;  // specific version (e.g. '1.0.0') or semver (e.g. 'minor', 'patch')\n  prereleaseId?: string;  // applicable when versionToTag is a pre-release. (e.g. \"dev\", for 1.0.0-dev.1)\n  message?: string;       // tag-message.\n}\nan example of the final data: '[{\"componentId\":\"ci.remote2/comp-b\",\"dependencies\":[\"ci.remote/comp1@0.0.2\"]}]'\n",
         "group": "development",
         "private": true,
         "remoteOp": true
     },
+    {
+        "name": "_snap <data>",
+        "alias": "",
+        "options": [
+            [
+                "",
+                "push",
+                "export the updated objects to the original scopes once done"
+            ],
+            [
+                "m",
+                "message <message>",
+                "log message describing the latest changes"
+            ],
+            [
+                "",
+                "build",
+                "run the build pipeline"
+            ],
+            [
+                "",
+                "skip-tests",
+                "skip running component tests during snap process"
+            ],
+            [
+                "",
+                "disable-snap-pipeline",
+                "skip the snap pipeline"
+            ],
+            [
+                "",
+                "force-deploy",
+                "run the deploy pipeline although the build failed"
+            ],
+            [
+                "i",
+                "ignore-issues [issues]",
+                "ignore component issues (shown in \"bit status\" as \"issues found\"), issues to ignore:\n[MissingPackagesDependenciesOnFs, MissingComponents, UntrackedDependencies, ResolveErrors, RelativeComponents, RelativeComponentsAuthored, ParseErrors, MissingDists, LegacyInsideHarmony, MissingDependenciesOnFs, ImportNonMainFiles, CustomModuleResolutionUsed, MultipleEnvs, MissingLinksFromNodeModulesToSrc, CircularDependencies, DuplicateComponentAndPackage]\nto ignore multiple issues, separate them by a comma and wrap with quotes. to ignore all issues, specify \"*\"."
+            ]
+        ],
+        "description": "snap components from a bare-scope",
+        "extendedDescription": "this command should be running from a new bare scope, it first imports the components it needs and then processes the snap.\nthe input data is a stringified JSON of an array of the following object.\n{\n  componentId: string;    // ids always have scope, so it's safe to parse them from string\n  dependencies?: string[]; // e.g. [teambit/compiler@1.0.0, teambit/tester@1.0.0]\n  aspects?: Record<string,any> // e.g. { \"teambit.react/react\": {}, \"teambit.envs/envs\": { \"env\": \"teambit.react/react\" } }\n  message?: string;       // tag-message.\n}\nan example of the final data: '[{\"componentId\":\"ci.remote2/comp-b\",\"message\": \"first snap\"}]'\n",
+        "group": "ungrouped",
+        "private": true
+    },
     {
         "name": "merge [values...]",
         "alias": "",
@@ -2746,6 +2796,11 @@
                 "",
                 "include-deps",
                 "EXPERIMENTAL. relevant for \"--pattern\". merge also dependencies of the given components"
+            ],
+            [
+                "j",
+                "json",
+                "output as json format"
             ]
         ],
         "description": "merge a remote lane into main via a bare-scope (not workspace)",

package/dist/cli-reference.mdx.js

@@ -1143,6 +1143,21 @@ function MDXContent(_ref) {
     "align": null
   }, (0, _react2.mdx)("inlineCode", {
     parentName: "td"
+  }, "--entire-lane")), (0, _react2.mdx)("td", {
+    parentName: "tr",
+    "align": "center"
+  }, (0, _react2.mdx)("inlineCode", {
+    parentName: "td"
+  }, "-e")), (0, _react2.mdx)("td", {
+    parentName: "tr",
+    "align": null
+  }, "write also new components that were introduced on the remote lane and do not exist locally")), (0, _react2.mdx)("tr", {
+    parentName: "tbody"
+  }, (0, _react2.mdx)("td", {
+    parentName: "tr",
+    "align": null
+  }, (0, _react2.mdx)("inlineCode", {
+    parentName: "td"
   }, "--verbose")), (0, _react2.mdx)("td", {
     parentName: "tr",
     "align": "center"