@teambit/harmony.content.cli-reference 1.95.218 → 1.95.219

package/cli-reference.json

@@ -819,7 +819,7 @@
         "name": "unset <component-pattern>",
         "options": [],
         "description": "un-sets an env from components that were previously set by \"bit env set\" or by a component template",
-        "extendedDescription": "keep in mind that this doesn't remove envs that are set via variants.\nin only removes envs that appear in the .bitmap file, which were previously configured via \"bit env set\".\nthe purpose of this command is to reset previously assigned envs to either allow variants configure the env or use the base node env.\nyou can use a `<pattern>` for multiple component ids, such as `bit env unset \"org.scope/utils/**\"`.\nuse comma to separate patterns and \"!\" to exclude. e.g. \"ui/**, !ui/button\"\nalways wrap the pattern with quotes to avoid collision with shell commands.\nuse `bit pattern --help` to understand patterns better and `bit pattern <pattern>` to validate the pattern.\n",
+        "extendedDescription": "keep in mind that this doesn't remove envs that are set via variants.\nin only removes envs that appear in the .bitmap file, which were previously configured via \"bit env set\".\nthe purpose of this command is to reset previously assigned envs to either allow variants configure the env or use the base node env.\nyou can use a `<pattern>` for multiple component ids, such as `bit env unset \"org.scope/utils/**\"`.\nuse comma to separate patterns and '!' to exclude. e.g. 'ui/**, !ui/button'\nalways wrap the pattern with single quotes to avoid collision with shell commands.\nuse `bit pattern --help` to understand patterns better and `bit pattern <pattern>` to validate the pattern.\n",
         "group": "development",
         "arguments": [
           {
@@ -996,7 +996,7 @@
         "name": "set <scope-name> [component-pattern]",
         "options": [],
         "description": "Sets the scope for specified component/s. If no component is specified, sets the default scope of the workspace",
-        "extendedDescription": "default scopes for components are set in the bitmap file. the default scope for a workspace is set in the workspace.jsonc.\na component is set with a scope (as oppose to default scope) only once it is versioned.'\n\nyou can use a `<pattern>` for multiple component ids, such as `bit scope set scope-name \"org.scope/utils/**\"`.\nuse comma to separate patterns and \"!\" to exclude. e.g. \"ui/**, !ui/button\"\nalways wrap the pattern with quotes to avoid collision with shell commands.\nuse `bit pattern --help` to understand patterns better and `bit pattern <pattern>` to validate the pattern.\n",
+        "extendedDescription": "default scopes for components are set in the bitmap file. the default scope for a workspace is set in the workspace.jsonc.\na component is set with a scope (as oppose to default scope) only once it is versioned.'\n\nyou can use a `<pattern>` for multiple component ids, such as `bit scope set scope-name \"org.scope/utils/**\"`.\nuse comma to separate patterns and '!' to exclude. e.g. 'ui/**, !ui/button'\nalways wrap the pattern with single quotes to avoid collision with shell commands.\nuse `bit pattern --help` to understand patterns better and `bit pattern <pattern>` to validate the pattern.\n",
         "group": "development",
         "arguments": [
           {
@@ -1089,7 +1089,7 @@
       ]
     ],
     "description": "eject components configuration (create a `component.json` file)",
-    "extendedDescription": "note this can be reversed at any time by snapping/tagging changes and deleting the component.json file \nyou can use a `<pattern>` for multiple component ids, such as `bit eject-conf \"org.scope/utils/**\"`.\nuse comma to separate patterns and \"!\" to exclude. e.g. \"ui/**, !ui/button\"\nalways wrap the pattern with quotes to avoid collision with shell commands.\nuse `bit pattern --help` to understand patterns better and `bit pattern <pattern>` to validate the pattern.\n",
+    "extendedDescription": "note this can be reversed at any time by snapping/tagging changes and deleting the component.json file \nyou can use a `<pattern>` for multiple component ids, such as `bit eject-conf \"org.scope/utils/**\"`.\nuse comma to separate patterns and '!' to exclude. e.g. 'ui/**, !ui/button'\nalways wrap the pattern with single quotes to avoid collision with shell commands.\nuse `bit pattern --help` to understand patterns better and `bit pattern <pattern>` to validate the pattern.\n",
     "group": "development",
     "private": false
   },
@@ -1227,28 +1227,28 @@
       ]
     ],
     "description": "list the component ids matching the given pattern",
-    "extendedDescription": "this command helps validating a pattern before using it in other commands.\na pattern can be a simple component-id or component-name. e.g. \"ui/button\".\na pattern can be used with wildcards for multiple component ids, e.g. \"org.scope/utils/**\" or \"**/utils/**\" to capture all org/scopes.\nto enter multiple patterns, separate them by a comma, e.g. \"ui/*, lib/*\"\nto exclude, use \"!\". e.g. \"ui/**, !ui/button\"\nalways wrap the pattern with quotes to avoid collision with shell commands.\nthe matching algorithm is from multimatch (@see https://github.com/sindresorhus/multimatch)\n",
+    "extendedDescription": "this command helps validating a pattern before using it in other commands.\na pattern can be a simple component-id or component-name. e.g. 'ui/button'.\na pattern can be used with wildcards for multiple component ids, e.g. 'org.scope/utils/**' or '**/utils/**' to capture all org/scopes.\nto enter multiple patterns, separate them by a comma, e.g. 'ui/*, lib/*'\nto exclude, use '!'. e.g. 'ui/**, !ui/button'\nalways wrap the pattern with single quotes to avoid collision with shell commands.\nthe matching algorithm is from multimatch (@see https://github.com/sindresorhus/multimatch)\nNOTE: always wrap the pattern with single quotes '' and not double \"\" to avoid collision with shell commands\n",
     "group": "development",
     "private": false,
     "examples": [
       {
-        "cmd": "bit pattern \"**\"",
+        "cmd": "bit pattern '**'",
         "description": "matches all components"
       },
       {
-        "cmd": "bit pattern \"*/ui/*\"",
+        "cmd": "bit pattern '*/ui/*'",
         "description": "matches components with any scope-name and the \"ui\" namespace. e.g. \"ui/button\" but not \"ui/elements/button\""
       },
       {
-        "cmd": "bit pattern \"*/ui/**\"",
+        "cmd": "bit pattern '*/ui/**'",
         "description": "matches components whose namespace starts with \"ui/\" e.g. \"ui/button\", \"ui/elements/button\""
       },
       {
-        "cmd": "bit pattern \"bar, foo\"",
+        "cmd": "bit pattern 'bar, foo'",
         "description": "matches two components: bar and foo"
       },
       {
-        "cmd": "bit pattern \"my-scope.org/**\"",
+        "cmd": "bit pattern 'my-scope.org/**'",
         "description": "matches all components of the scope \"my-scope.org\""
       }
     ]
@@ -4148,7 +4148,7 @@
       ]
     ],
     "description": "shows the API schema of the specified component/s.",
-    "extendedDescription": "you can use a `<pattern>` for multiple component ids, such as `bit schema \"org.scope/utils/**\"`.\nuse comma to separate patterns and \"!\" to exclude. e.g. \"ui/**, !ui/button\"\nalways wrap the pattern with quotes to avoid collision with shell commands.\nuse `bit pattern --help` to understand patterns better and `bit pattern <pattern>` to validate the pattern.\n",
+    "extendedDescription": "you can use a `<pattern>` for multiple component ids, such as `bit schema \"org.scope/utils/**\"`.\nuse comma to separate patterns and '!' to exclude. e.g. 'ui/**, !ui/button'\nalways wrap the pattern with single quotes to avoid collision with shell commands.\nuse `bit pattern --help` to understand patterns better and `bit pattern <pattern>` to validate the pattern.\n",
     "group": "development",
     "private": false
   },

package/cli-reference.mdx

@@ -649,8 +649,8 @@ By default the component files will be removed from the workspace
 **Description**: eject components configuration (create a `component.json` file)  
 note this can be reversed at any time by snapping/tagging changes and deleting the component.json file  
 you can use a `<pattern>` for multiple component ids, such as `bit eject-conf "org.scope/utils/**"`.  
-use comma to separate patterns and "!" to exclude. e.g. "ui/\*\*, !ui/button"  
-always wrap the pattern with quotes to avoid collision with shell commands.  
+use comma to separate patterns and '!' to exclude. e.g. 'ui/\*\*, !ui/button'  
+always wrap the pattern with single quotes to avoid collision with shell commands.  
 use `bit pattern --help` to understand patterns better and `bit pattern <pattern>` to validate the pattern.
 
 `bit eject-conf <pattern>`
@@ -709,8 +709,8 @@ keep in mind that this doesn't remove envs that are set via variants.
 in only removes envs that appear in the .bitmap file, which were previously configured via "bit env set".  
 the purpose of this command is to reset previously assigned envs to either allow variants configure the env or use the base node env.  
 you can use a `<pattern>` for multiple component ids, such as `bit env unset "org.scope/utils/**"`.  
-use comma to separate patterns and "!" to exclude. e.g. "ui/\*\*, !ui/button"  
-always wrap the pattern with quotes to avoid collision with shell commands.  
+use comma to separate patterns and '!' to exclude. e.g. 'ui/\*\*, !ui/button'  
+always wrap the pattern with single quotes to avoid collision with shell commands.  
 use `bit pattern --help` to understand patterns better and `bit pattern <pattern>` to validate the pattern.
 
 | **Arg**             |                                                                                                   **Description**                                                                                                   |
@@ -1410,12 +1410,13 @@ move files or directories of component(s)
 
 **Description**: list the component ids matching the given pattern  
 this command helps validating a pattern before using it in other commands.  
-a pattern can be a simple component-id or component-name. e.g. "ui/button".  
-a pattern can be used with wildcards for multiple component ids, e.g. "org.scope/utils/**" or "**/utils/**" to capture all org/scopes.  
-to enter multiple patterns, separate them by a comma, e.g. "ui/_, lib/_"  
-to exclude, use "!". e.g. "ui/**, !ui/button"  
-always wrap the pattern with quotes to avoid collision with shell commands.  
-the matching algorithm is from multimatch (@see https://github.com/sindresorhus/multimatch)
+a pattern can be a simple component-id or component-name. e.g. 'ui/button'.  
+a pattern can be used with wildcards for multiple component ids, e.g. 'org.scope/utils/**' or '**/utils/**' to capture all org/scopes.  
+to enter multiple patterns, separate them by a comma, e.g. 'ui/_, lib/_'  
+to exclude, use '!'. e.g. 'ui/**, !ui/button'  
+always wrap the pattern with single quotes to avoid collision with shell commands.  
+the matching algorithm is from multimatch (@see https://github.com/sindresorhus/multimatch)  
+NOTE: always wrap the pattern with single quotes '' and not double "" to avoid collision with shell commands
 
 `bit pattern <pattern>`
 
@@ -1592,8 +1593,8 @@ https://https://bit.dev//components/tags#undoing-a-tag
 
 **Description**: shows the API schema of the specified component/s.  
 you can use a `<pattern>` for multiple component ids, such as `bit schema "org.scope/utils/**"`.  
-use comma to separate patterns and "!" to exclude. e.g. "ui/\*\*, !ui/button"  
-always wrap the pattern with quotes to avoid collision with shell commands.  
+use comma to separate patterns and '!' to exclude. e.g. 'ui/\*\*, !ui/button'  
+always wrap the pattern with single quotes to avoid collision with shell commands.  
 use `bit pattern --help` to understand patterns better and `bit pattern <pattern>` to validate the pattern.
 
 `bit schema <pattern>`
@@ -1619,8 +1620,8 @@ default scopes for components are set in the bitmap file. the default scope for
 a component is set with a scope (as oppose to default scope) only once it is versioned.'
 
 you can use a `<pattern>` for multiple component ids, such as `bit scope set scope-name "org.scope/utils/**"`.  
-use comma to separate patterns and "!" to exclude. e.g. "ui/\*\*, !ui/button"  
-always wrap the pattern with quotes to avoid collision with shell commands.  
+use comma to separate patterns and '!' to exclude. e.g. 'ui/\*\*, !ui/button'  
+always wrap the pattern with single quotes to avoid collision with shell commands.  
 use `bit pattern --help` to understand patterns better and `bit pattern <pattern>` to validate the pattern.
 
 | **Arg**             |                                                                                                   **Description**                                                                                                   |

package/dist/cli-reference.composition.d.ts

@@ -1,2 +1,2 @@
-import React from 'react';
-export declare const BasicCliReference: () => React.JSX.Element;
+/// <reference types="react" />
+export declare const BasicCliReference: () => JSX.Element;

package/dist/cli-reference.json

@@ -819,7 +819,7 @@
                 "name": "unset <component-pattern>",
                 "options": [],
                 "description": "un-sets an env from components that were previously set by \"bit env set\" or by a component template",
-                "extendedDescription": "keep in mind that this doesn't remove envs that are set via variants.\nin only removes envs that appear in the .bitmap file, which were previously configured via \"bit env set\".\nthe purpose of this command is to reset previously assigned envs to either allow variants configure the env or use the base node env.\nyou can use a `<pattern>` for multiple component ids, such as `bit env unset \"org.scope/utils/**\"`.\nuse comma to separate patterns and \"!\" to exclude. e.g. \"ui/**, !ui/button\"\nalways wrap the pattern with quotes to avoid collision with shell commands.\nuse `bit pattern --help` to understand patterns better and `bit pattern <pattern>` to validate the pattern.\n",
+                "extendedDescription": "keep in mind that this doesn't remove envs that are set via variants.\nin only removes envs that appear in the .bitmap file, which were previously configured via \"bit env set\".\nthe purpose of this command is to reset previously assigned envs to either allow variants configure the env or use the base node env.\nyou can use a `<pattern>` for multiple component ids, such as `bit env unset \"org.scope/utils/**\"`.\nuse comma to separate patterns and '!' to exclude. e.g. 'ui/**, !ui/button'\nalways wrap the pattern with single quotes to avoid collision with shell commands.\nuse `bit pattern --help` to understand patterns better and `bit pattern <pattern>` to validate the pattern.\n",
                 "group": "development",
                 "arguments": [
                     {
@@ -996,7 +996,7 @@
                 "name": "set <scope-name> [component-pattern]",
                 "options": [],
                 "description": "Sets the scope for specified component/s. If no component is specified, sets the default scope of the workspace",
-                "extendedDescription": "default scopes for components are set in the bitmap file. the default scope for a workspace is set in the workspace.jsonc.\na component is set with a scope (as oppose to default scope) only once it is versioned.'\n\nyou can use a `<pattern>` for multiple component ids, such as `bit scope set scope-name \"org.scope/utils/**\"`.\nuse comma to separate patterns and \"!\" to exclude. e.g. \"ui/**, !ui/button\"\nalways wrap the pattern with quotes to avoid collision with shell commands.\nuse `bit pattern --help` to understand patterns better and `bit pattern <pattern>` to validate the pattern.\n",
+                "extendedDescription": "default scopes for components are set in the bitmap file. the default scope for a workspace is set in the workspace.jsonc.\na component is set with a scope (as oppose to default scope) only once it is versioned.'\n\nyou can use a `<pattern>` for multiple component ids, such as `bit scope set scope-name \"org.scope/utils/**\"`.\nuse comma to separate patterns and '!' to exclude. e.g. 'ui/**, !ui/button'\nalways wrap the pattern with single quotes to avoid collision with shell commands.\nuse `bit pattern --help` to understand patterns better and `bit pattern <pattern>` to validate the pattern.\n",
                 "group": "development",
                 "arguments": [
                     {
@@ -1089,7 +1089,7 @@
             ]
         ],
         "description": "eject components configuration (create a `component.json` file)",
-        "extendedDescription": "note this can be reversed at any time by snapping/tagging changes and deleting the component.json file \nyou can use a `<pattern>` for multiple component ids, such as `bit eject-conf \"org.scope/utils/**\"`.\nuse comma to separate patterns and \"!\" to exclude. e.g. \"ui/**, !ui/button\"\nalways wrap the pattern with quotes to avoid collision with shell commands.\nuse `bit pattern --help` to understand patterns better and `bit pattern <pattern>` to validate the pattern.\n",
+        "extendedDescription": "note this can be reversed at any time by snapping/tagging changes and deleting the component.json file \nyou can use a `<pattern>` for multiple component ids, such as `bit eject-conf \"org.scope/utils/**\"`.\nuse comma to separate patterns and '!' to exclude. e.g. 'ui/**, !ui/button'\nalways wrap the pattern with single quotes to avoid collision with shell commands.\nuse `bit pattern --help` to understand patterns better and `bit pattern <pattern>` to validate the pattern.\n",
         "group": "development",
         "private": false
     },
@@ -1227,28 +1227,28 @@
             ]
         ],
         "description": "list the component ids matching the given pattern",
-        "extendedDescription": "this command helps validating a pattern before using it in other commands.\na pattern can be a simple component-id or component-name. e.g. \"ui/button\".\na pattern can be used with wildcards for multiple component ids, e.g. \"org.scope/utils/**\" or \"**/utils/**\" to capture all org/scopes.\nto enter multiple patterns, separate them by a comma, e.g. \"ui/*, lib/*\"\nto exclude, use \"!\". e.g. \"ui/**, !ui/button\"\nalways wrap the pattern with quotes to avoid collision with shell commands.\nthe matching algorithm is from multimatch (@see https://github.com/sindresorhus/multimatch)\n",
+        "extendedDescription": "this command helps validating a pattern before using it in other commands.\na pattern can be a simple component-id or component-name. e.g. 'ui/button'.\na pattern can be used with wildcards for multiple component ids, e.g. 'org.scope/utils/**' or '**/utils/**' to capture all org/scopes.\nto enter multiple patterns, separate them by a comma, e.g. 'ui/*, lib/*'\nto exclude, use '!'. e.g. 'ui/**, !ui/button'\nalways wrap the pattern with single quotes to avoid collision with shell commands.\nthe matching algorithm is from multimatch (@see https://github.com/sindresorhus/multimatch)\nNOTE: always wrap the pattern with single quotes '' and not double \"\" to avoid collision with shell commands\n",
         "group": "development",
         "private": false,
         "examples": [
             {
-                "cmd": "bit pattern \"**\"",
+                "cmd": "bit pattern '**'",
                 "description": "matches all components"
             },
             {
-                "cmd": "bit pattern \"*/ui/*\"",
+                "cmd": "bit pattern '*/ui/*'",
                 "description": "matches components with any scope-name and the \"ui\" namespace. e.g. \"ui/button\" but not \"ui/elements/button\""
             },
             {
-                "cmd": "bit pattern \"*/ui/**\"",
+                "cmd": "bit pattern '*/ui/**'",
                 "description": "matches components whose namespace starts with \"ui/\" e.g. \"ui/button\", \"ui/elements/button\""
             },
             {
-                "cmd": "bit pattern \"bar, foo\"",
+                "cmd": "bit pattern 'bar, foo'",
                 "description": "matches two components: bar and foo"
             },
             {
-                "cmd": "bit pattern \"my-scope.org/**\"",
+                "cmd": "bit pattern 'my-scope.org/**'",
                 "description": "matches all components of the scope \"my-scope.org\""
             }
         ]
@@ -4148,7 +4148,7 @@
             ]
         ],
         "description": "shows the API schema of the specified component/s.",
-        "extendedDescription": "you can use a `<pattern>` for multiple component ids, such as `bit schema \"org.scope/utils/**\"`.\nuse comma to separate patterns and \"!\" to exclude. e.g. \"ui/**, !ui/button\"\nalways wrap the pattern with quotes to avoid collision with shell commands.\nuse `bit pattern --help` to understand patterns better and `bit pattern <pattern>` to validate the pattern.\n",
+        "extendedDescription": "you can use a `<pattern>` for multiple component ids, such as `bit schema \"org.scope/utils/**\"`.\nuse comma to separate patterns and '!' to exclude. e.g. 'ui/**, !ui/button'\nalways wrap the pattern with single quotes to avoid collision with shell commands.\nuse `bit pattern --help` to understand patterns better and `bit pattern <pattern>` to validate the pattern.\n",
         "group": "development",
         "private": false
     },

package/dist/cli-reference.mdx.js

@@ -2997,9 +2997,9 @@ function MDXContent(_ref) {
     parentName: "p"
   }, "bit eject-conf \"org.scope/utils/**\""), ".", (0, _react2.mdx)("br", {
     parentName: "p"
-  }), "\n", "use comma to separate patterns and \"!\" to exclude. e.g. \"ui/", "*", "*", ", !ui/button\"", (0, _react2.mdx)("br", {
+  }), "\n", "use comma to separate patterns and '!' to exclude. e.g. 'ui/", "*", "*", ", !ui/button'", (0, _react2.mdx)("br", {
     parentName: "p"
-  }), "\n", "always wrap the pattern with quotes to avoid collision with shell commands.", (0, _react2.mdx)("br", {
+  }), "\n", "always wrap the pattern with single quotes to avoid collision with shell commands.", (0, _react2.mdx)("br", {
     parentName: "p"
   }), "\n", "use ", (0, _react2.mdx)("inlineCode", {
     parentName: "p"
@@ -3204,9 +3204,9 @@ function MDXContent(_ref) {
     parentName: "p"
   }, "bit env unset \"org.scope/utils/**\""), ".", (0, _react2.mdx)("br", {
     parentName: "p"
-  }), "\n", "use comma to separate patterns and \"!\" to exclude. e.g. \"ui/", "*", "*", ", !ui/button\"", (0, _react2.mdx)("br", {
+  }), "\n", "use comma to separate patterns and '!' to exclude. e.g. 'ui/", "*", "*", ", !ui/button'", (0, _react2.mdx)("br", {
     parentName: "p"
-  }), "\n", "always wrap the pattern with quotes to avoid collision with shell commands.", (0, _react2.mdx)("br", {
+  }), "\n", "always wrap the pattern with single quotes to avoid collision with shell commands.", (0, _react2.mdx)("br", {
     parentName: "p"
   }), "\n", "use ", (0, _react2.mdx)("inlineCode", {
     parentName: "p"
@@ -7172,26 +7172,28 @@ function MDXContent(_ref) {
     parentName: "p"
   }), "\n", "this command helps validating a pattern before using it in other commands.", (0, _react2.mdx)("br", {
     parentName: "p"
-  }), "\n", "a pattern can be a simple component-id or component-name. e.g. \"ui/button\".", (0, _react2.mdx)("br", {
+  }), "\n", "a pattern can be a simple component-id or component-name. e.g. 'ui/button'.", (0, _react2.mdx)("br", {
     parentName: "p"
-  }), "\n", "a pattern can be used with wildcards for multiple component ids, e.g. \"org.scope/utils/", (0, _react2.mdx)("strong", {
+  }), "\n", "a pattern can be used with wildcards for multiple component ids, e.g. 'org.scope/utils/", (0, _react2.mdx)("strong", {
     parentName: "p"
-  }, "\" or \""), "/utils/", (0, _react2.mdx)("strong", {
+  }, "' or '"), "/utils/", (0, _react2.mdx)("strong", {
     parentName: "p"
-  }, "\" to capture all org/scopes.", (0, _react2.mdx)("br", {
+  }, "' to capture all org/scopes.", (0, _react2.mdx)("br", {
     parentName: "strong"
-  }), "to enter multiple patterns, separate them by a comma, e.g. \"ui/", (0, _react2.mdx)("em", {
+  }), "to enter multiple patterns, separate them by a comma, e.g. 'ui/", (0, _react2.mdx)("em", {
     parentName: "strong"
-  }, ", lib/"), "\"", (0, _react2.mdx)("br", {
+  }, ", lib/"), "'", (0, _react2.mdx)("br", {
     parentName: "strong"
-  }), "to exclude, use \"!\". e.g. \"ui/"), ", !ui/button\"", (0, _react2.mdx)("br", {
+  }), "to exclude, use '!'. e.g. 'ui/"), ", !ui/button'", (0, _react2.mdx)("br", {
     parentName: "p"
-  }), "\n", "always wrap the pattern with quotes to avoid collision with shell commands.", (0, _react2.mdx)("br", {
+  }), "\n", "always wrap the pattern with single quotes to avoid collision with shell commands.", (0, _react2.mdx)("br", {
     parentName: "p"
   }), "\n", "the matching algorithm is from multimatch (@see ", (0, _react2.mdx)("a", {
     parentName: "p",
     "href": "https://github.com/sindresorhus/multimatch"
-  }, "https://github.com/sindresorhus/multimatch"), ")"), (0, _react2.mdx)("p", null, (0, _react2.mdx)("inlineCode", {
+  }, "https://github.com/sindresorhus/multimatch"), ")", (0, _react2.mdx)("br", {
+    parentName: "p"
+  }), "\n", "NOTE: always wrap the pattern with single quotes '' and not double \"\" to avoid collision with shell commands"), (0, _react2.mdx)("p", null, (0, _react2.mdx)("inlineCode", {
     parentName: "p"
   }, "bit pattern <pattern>")), (0, _react2.mdx)("table", null, (0, _react2.mdx)("thead", {
     parentName: "table"
@@ -8013,9 +8015,9 @@ function MDXContent(_ref) {
     parentName: "p"
   }, "bit schema \"org.scope/utils/**\""), ".", (0, _react2.mdx)("br", {
     parentName: "p"
-  }), "\n", "use comma to separate patterns and \"!\" to exclude. e.g. \"ui/", "*", "*", ", !ui/button\"", (0, _react2.mdx)("br", {
+  }), "\n", "use comma to separate patterns and '!' to exclude. e.g. 'ui/", "*", "*", ", !ui/button'", (0, _react2.mdx)("br", {
     parentName: "p"
-  }), "\n", "always wrap the pattern with quotes to avoid collision with shell commands.", (0, _react2.mdx)("br", {
+  }), "\n", "always wrap the pattern with single quotes to avoid collision with shell commands.", (0, _react2.mdx)("br", {
     parentName: "p"
   }), "\n", "use ", (0, _react2.mdx)("inlineCode", {
     parentName: "p"
@@ -8079,9 +8081,9 @@ function MDXContent(_ref) {
     parentName: "p"
   }, "bit scope set scope-name \"org.scope/utils/**\""), ".", (0, _react2.mdx)("br", {
     parentName: "p"
-  }), "\n", "use comma to separate patterns and \"!\" to exclude. e.g. \"ui/", "*", "*", ", !ui/button\"", (0, _react2.mdx)("br", {
+  }), "\n", "use comma to separate patterns and '!' to exclude. e.g. 'ui/", "*", "*", ", !ui/button'", (0, _react2.mdx)("br", {
     parentName: "p"
-  }), "\n", "always wrap the pattern with quotes to avoid collision with shell commands.", (0, _react2.mdx)("br", {
+  }), "\n", "always wrap the pattern with single quotes to avoid collision with shell commands.", (0, _react2.mdx)("br", {
     parentName: "p"
   }), "\n", "use ", (0, _react2.mdx)("inlineCode", {
     parentName: "p"