@teambit/harmony.content.cli-reference 1.95.58 → 1.95.59

package/cli-reference.json

@@ -3347,7 +3347,7 @@
       ]
     ],
     "description": "export components from the workspace to remote scopes",
-    "extendedDescription": "bit export => export all staged components to their current scope, if checked out to a lane, export the lane as well\n`bit export [id...]` => export the given ids to their current scope\n\nhttps://bit.dev/docs/components/exporting-components\nyou can use a pattern for multiple ids, such as bit export remote-scope \"utils/*\". (wrap the pattern with quotes to avoid collision with shell commands)",
+    "extendedDescription": "bit export => export all staged components to their current scope, if checked out to a lane, export the lane as well\n  `bit export [id...]` => export the given ids to their current scope\n  you can use a pattern for multiple ids, such as bit export remote-scope \"utils/*\". (wrap the pattern with quotes to avoid collision with shell commands)",
     "group": "collaborate",
     "private": false,
     "remoteOp": true,

package/cli-reference.mdx

@@ -558,10 +558,8 @@ use `bit pattern --help` to understand patterns better and `bit pattern <pattern
 **Workspace only**: yes  
 **Description**: export components from the workspace to remote scopes  
 bit export => export all staged components to their current scope, if checked out to a lane, export the lane as well  
-`bit export [id...]` => export the given ids to their current scope
-
-https://bit.dev/docs/components/exporting-components  
-you can use a pattern for multiple ids, such as bit export remote-scope "utils/\*". (wrap the pattern with quotes to avoid collision with shell commands)
+ `bit export [id...]` => export the given ids to their current scope  
+ you can use a pattern for multiple ids, such as bit export remote-scope "utils/\*". (wrap the pattern with quotes to avoid collision with shell commands)
 
 `bit export [component-patterns...]`
 

package/dist/cli-reference.json

@@ -3347,7 +3347,7 @@
             ]
         ],
         "description": "export components from the workspace to remote scopes",
-        "extendedDescription": "bit export => export all staged components to their current scope, if checked out to a lane, export the lane as well\n`bit export [id...]` => export the given ids to their current scope\n\nhttps://bit.dev/docs/components/exporting-components\nyou can use a pattern for multiple ids, such as bit export remote-scope \"utils/*\". (wrap the pattern with quotes to avoid collision with shell commands)",
+        "extendedDescription": "bit export => export all staged components to their current scope, if checked out to a lane, export the lane as well\n  `bit export [id...]` => export the given ids to their current scope\n  you can use a pattern for multiple ids, such as bit export remote-scope \"utils/*\". (wrap the pattern with quotes to avoid collision with shell commands)",
         "group": "collaborate",
         "private": false,
         "remoteOp": true,

package/dist/cli-reference.mdx.js

@@ -2174,12 +2174,9 @@ function MDXContent(_ref) {
     parentName: "p"
   }), "\n", "bit export => export all staged components to their current scope, if checked out to a lane, export the lane as well", (0, _react2.mdx)("br", {
     parentName: "p"
-  }), "\n", (0, _react2.mdx)("inlineCode", {
+  }), "\n", "", (0, _react2.mdx)("inlineCode", {
     parentName: "p"
-  }, "bit export [id...]"), " => export the given ids to their current scope"), (0, _react2.mdx)("p", null, (0, _react2.mdx)("a", {
-    parentName: "p",
-    "href": "https://bit.dev/docs/components/exporting-components"
-  }, "https://bit.dev/docs/components/exporting-components"), (0, _react2.mdx)("br", {
+  }, "bit export [id...]"), " => export the given ids to their current scope", (0, _react2.mdx)("br", {
     parentName: "p"
   }), "\n", "you can use a pattern for multiple ids, such as bit export remote-scope \"utils/", "*", "\". (wrap the pattern with quotes to avoid collision with shell commands)"), (0, _react2.mdx)("p", null, (0, _react2.mdx)("inlineCode", {
     parentName: "p"