@teambit/harmony.content.cli-reference 1.95.44 → 1.95.45

package/cli-reference.json

@@ -2005,7 +2005,7 @@
       ]
     ],
     "description": "create an immutable and exportable component snapshot, tagged with a release version.",
-    "extendedDescription": "if no patterns are provided, it will tag all new and modified components.\nif patterns are entered, you can specify a version per pattern using \"@\" sign, e.g. bit tag foo@1.0.0 bar@minor baz@major\nhttps://bit.dev/components/tags",
+    "extendedDescription": "if no patterns are provided, it will tag all new and modified components.\nif patterns are entered, you can specify a version per pattern using \"@\" sign, e.g. bit tag foo@1.0.0 bar@minor baz@major",
     "group": "development",
     "private": false,
     "remoteOp": true,

package/cli-reference.mdx

@@ -1125,8 +1125,7 @@ use `bit pattern --help` to understand patterns better and `bit pattern <pattern
 **Workspace only**: yes  
 **Description**: create an immutable and exportable component snapshot, tagged with a release version.  
 if no patterns are provided, it will tag all new and modified components.  
-if patterns are entered, you can specify a version per pattern using "@" sign, e.g. bit tag foo@1.0.0 bar@minor baz@major  
-https://bit.dev/components/tags
+if patterns are entered, you can specify a version per pattern using "@" sign, e.g. bit tag foo@1.0.0 bar@minor baz@major
 
 `bit tag [component-patterns...]`
 

package/dist/cli-reference.json

@@ -2005,7 +2005,7 @@
             ]
         ],
         "description": "create an immutable and exportable component snapshot, tagged with a release version.",
-        "extendedDescription": "if no patterns are provided, it will tag all new and modified components.\nif patterns are entered, you can specify a version per pattern using \"@\" sign, e.g. bit tag foo@1.0.0 bar@minor baz@major\nhttps://bit.dev/components/tags",
+        "extendedDescription": "if no patterns are provided, it will tag all new and modified components.\nif patterns are entered, you can specify a version per pattern using \"@\" sign, e.g. bit tag foo@1.0.0 bar@minor baz@major",
         "group": "development",
         "private": false,
         "remoteOp": true,

package/dist/cli-reference.mdx.js

@@ -4923,12 +4923,7 @@ function MDXContent(_ref) {
   }), "\n", "if patterns are entered, you can specify a version per pattern using \"@\" sign, e.g. bit tag ", (0, _react2.mdx)("a", {
     parentName: "p",
     "href": "mailto:foo@1.0.0"
-  }, "foo@1.0.0"), " bar@minor baz@major", (0, _react2.mdx)("br", {
-    parentName: "p"
-  }), "\n", (0, _react2.mdx)("a", {
-    parentName: "p",
-    "href": "https://bit.dev/components/tags"
-  }, "https://bit.dev/components/tags")), (0, _react2.mdx)("p", null, (0, _react2.mdx)("inlineCode", {
+  }, "foo@1.0.0"), " bar@minor baz@major"), (0, _react2.mdx)("p", null, (0, _react2.mdx)("inlineCode", {
     parentName: "p"
   }, "bit tag [component-patterns...]")), (0, _react2.mdx)("table", null, (0, _react2.mdx)("thead", {
     parentName: "table"