From 6bec2b0d56330f254630ea0e4ba4b26af8cc2bc6 Mon Sep 17 00:00:00 2001
From: raj pandey <raj.pandey@contentstack.com>
Date: Wed, 5 Aug 2026 17:14:18 +0530
Subject: [PATCH 1/4] docs(cli): replace oclif command dump with concise README
 and plugin index

Reduces packages/contentstack/README.md from 4493 lines to ~72. Replaces
the auto-generated full command reference with:
- Bundled plugins table (14 plugins) linking each to its npm page
- Installable plugins table (7 opt-in plugins) with install instruction
- Accurate descriptions, bulk-publish vs bulk-operations note, and a
  footnote explaining the two legacy unscoped package names

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---
 packages/contentstack/README.md | 4516 +------------------------------
 1 file changed, 47 insertions(+), 4469 deletions(-)

diff --git a/packages/contentstack/README.md b/packages/contentstack/README.md
index 761ff3663b..520ad1ee1b 100644
--- a/packages/contentstack/README.md
+++ b/packages/contentstack/README.md
@@ -1,4493 +1,71 @@
 # @contentstack/cli
 
-Use Contentstack Command-line Interface to command Contentstack for executing a set of operations from the terminal. To get started with CLI, refer to the [CLI’s documentation](https://www.contentstack.com/docs/developers/cli)
+Use Contentstack Command-line Interface (CLI) to interact with Contentstack directly from your terminal.
 
 [![License](https://img.shields.io/npm/l/@contentstack/cli)](https://github.com/contentstack/cli/blob/main/LICENSE)
+[![npm](https://img.shields.io/npm/v/@contentstack/cli)](https://www.npmjs.com/package/@contentstack/cli)
 
-<!-- toc -->
-* [@contentstack/cli](#contentstackcli)
-* [Requirements](#requirements)
-* [Usage](#usage)
-* [Commands](#commands)
-<!-- tocstop -->
+## Requirements
 
-# Requirements
+Node.js v22 or higher — download from [nodejs.org](https://nodejs.org/).
 
-- **Node.js v22 or higher** is required. Download it from [nodejs.org](https://nodejs.org/).
-
-> **Note:** Starting from this version, Contentstack CLI requires Node.js 22+. Node.js 22 is the current LTS release and includes important compatibility improvements for modern JavaScript modules.
-
-# Usage
-
-<!-- usage -->
-```sh-session
-$ npm install -g @contentstack/cli
-$ csdx COMMAND
-running command...
-$ csdx (--version|-v)
-@contentstack/cli/1.65.0 darwin-arm64 node-v22.13.1
-$ csdx --help [COMMAND]
-USAGE
-  $ csdx COMMAND
-...
-```
-<!-- usagestop -->
-
-# Commands
-
-<!-- commands -->
-* [`csdx audit`](#csdx-audit)
-* [`csdx audit:fix`](#csdx-auditfix)
-* [`csdx auth:login`](#csdx-authlogin)
-* [`csdx auth:logout`](#csdx-authlogout)
-* [`csdx auth:tokens`](#csdx-authtokens)
-* [`csdx auth:tokens:add [-a <value>] [--delivery] [--management] [-e <value>] [-k <value>] [-y] [--token <value>]`](#csdx-authtokensadd--a-value---delivery---management--e-value--k-value--y---token-value)
-* [`csdx auth:tokens:remove`](#csdx-authtokensremove)
-* [`csdx auth:whoami`](#csdx-authwhoami)
-* [`csdx cm:assets:publish [-a <value>] [--retry-failed <value>] [-e <value>] [--folder-uid <value>] [--backup-dir <value>] [--bulk-publish <value>] [-c <value>] [-y] [--locales <value>] [--branch <value>] [--delivery-token <value>] [--source-env <value>]`](#csdx-cmassetspublish--a-value---retry-failed-value--e-value---folder-uid-value---backup-dir-value---bulk-publish-value--c-value--y---locales-value---branch-value---delivery-token-value---source-env-value)
-* [`csdx cm:assets:unpublish`](#csdx-cmassetsunpublish)
-* [`csdx cm:bootstrap`](#csdx-cmbootstrap)
-* [`csdx cm:branches`](#csdx-cmbranches)
-* [`csdx cm:branches:create`](#csdx-cmbranchescreate)
-* [`csdx cm:branches:delete [-uid <value>] [-k <value>]`](#csdx-cmbranchesdelete--uid-value--k-value)
-* [`csdx cm:branches:diff [--base-branch <value>] [--compare-branch <value>] [-k <value>][--module <value>] [--format <value>] [--csv-path <value>]`](#csdx-cmbranchesdiff---base-branch-value---compare-branch-value--k-value--module-value---format-value---csv-path-value)
-* [`csdx cm:branches:merge [-k <value>][--compare-branch <value>] [--no-revert] [--export-summary-path <value>] [--use-merge-summary <value>] [--comment <value>] [--base-branch <value>]`](#csdx-cmbranchesmerge--k-value--compare-branch-value---no-revert---export-summary-path-value---use-merge-summary-value---comment-value---base-branch-value)
-* [`csdx cm:branches:merge-status -k <value> --merge-uid <value>`](#csdx-cmbranchesmerge-status--k-value---merge-uid-value)
-* [`csdx cm:bulk-publish`](#csdx-cmbulk-publish)
-* [`csdx cm:entries:update-and-publish [-a <value>] [--retry-failed <value>] [--bulk-publish <value>] [--content-types <value>] [-t <value>] [-e <value>] [-c <value>] [-y] [--locales <value>] [--branch <value>]`](#csdx-cmentriesupdate-and-publish--a-value---retry-failed-value---bulk-publish-value---content-types-value--t-value--e-value--c-value--y---locales-value---branch-value)
-* [`csdx cm:assets:publish [-a <value>] [--retry-failed <value>] [-e <value>] [--folder-uid <value>] [--backup-dir <value>] [--bulk-publish <value>] [-c <value>] [-y] [--locales <value>] [--branch <value>] [--delivery-token <value>] [--source-env <value>]`](#csdx-cmassetspublish--a-value---retry-failed-value--e-value---folder-uid-value---backup-dir-value---bulk-publish-value--c-value--y---locales-value---branch-value---delivery-token-value---source-env-value)
-* [`csdx cm:bulk-publish:clear`](#csdx-cmbulk-publishclear)
-* [`csdx cm:bulk-publish:configure`](#csdx-cmbulk-publishconfigure)
-* [`csdx cm:bulk-publish:cross-publish [-a <value>] [--retry-failed <value>] [--bulk-publish <value>] [--content-type <value>] [--locales <value>] [--source-env <value>] [--environments <value>] [--delivery-token <value>] [-c <value>] [-y] [--branch <value>] [--onlyAssets] [--onlyEntries] [--include-variants]`](#csdx-cmbulk-publishcross-publish--a-value---retry-failed-value---bulk-publish-value---content-type-value---locales-value---source-env-value---environments-value---delivery-token-value--c-value--y---branch-value---onlyassets---onlyentries---include-variants)
-* [`csdx cm:entries:publish [-a <value>] [--retry-failed <value>] [--bulk-publish <value>] [--publish-all-content-types] [--content-types <value>] [--locales <value>] [-e <value>] [-c <value>] [-y] [--branch <value>] [--delivery-token <value>] [--source-env <value>] [--entry-uid <value>] [--include-variants]`](#csdx-cmentriespublish--a-value---retry-failed-value---bulk-publish-value---publish-all-content-types---content-types-value---locales-value--e-value--c-value--y---branch-value---delivery-token-value---source-env-value---entry-uid-value---include-variants)
-* [`csdx cm:entries:publish-modified [-a <value>] [--retry-failed <value>] [--bulk-publish <value>] [--source-env <value>] [--content-types <value>] [--locales <value>] [-e <value>] [-c <value>] [-y] [--branch <value>]`](#csdx-cmentriespublish-modified--a-value---retry-failed-value---bulk-publish-value---source-env-value---content-types-value---locales-value--e-value--c-value--y---branch-value)
-* [`csdx cm:entries:publish-non-localized-fields [-a <value>] [--retry-failed <value>] [--bulk-publish <value>] [--source-env <value>] [--content-types <value>] [-e <value>] [-c <value>] [-y] [--branch <value>]`](#csdx-cmentriespublish-non-localized-fields--a-value---retry-failed-value---bulk-publish-value---source-env-value---content-types-value--e-value--c-value--y---branch-value)
-* [`csdx cm:bulk-publish:revert`](#csdx-cmbulk-publishrevert)
-* [`csdx csdx cm:stacks:unpublish [-a <value>] [-e <value>] [-c <value>] [-y] [--locale <value>] [--branch <value>] [--retry-failed <value>] [--bulk-unpublish <value>] [--content-type <value>] [--delivery-token <value>] [--only-assets] [--only-entries]`](#csdx-csdx-cmstacksunpublish--a-value--e-value--c-value--y---locale-value---branch-value---retry-failed-value---bulk-unpublish-value---content-type-value---delivery-token-value---only-assets---only-entries)
-* [`csdx cm:entries:publish-only-unpublished [-a <value>] [--retry-failed <value>] [--bulk-publish <value>] [--source-env <value>] [--content-types <value>] [--locales <value>] [-e <value>] [-c <value>] [-y] [--branch <value>]`](#csdx-cmentriespublish-only-unpublished--a-value---retry-failed-value---bulk-publish-value---source-env-value---content-types-value---locales-value--e-value--c-value--y---branch-value)
-* [`csdx cm:entries:migrate-html-rte`](#csdx-cmentriesmigrate-html-rte)
-* [`csdx cm:entries:publish [-a <value>] [--retry-failed <value>] [--bulk-publish <value>] [--publish-all-content-types] [--content-types <value>] [--locales <value>] [-e <value>] [-c <value>] [-y] [--branch <value>] [--delivery-token <value>] [--source-env <value>] [--entry-uid <value>] [--include-variants]`](#csdx-cmentriespublish--a-value---retry-failed-value---bulk-publish-value---publish-all-content-types---content-types-value---locales-value--e-value--c-value--y---branch-value---delivery-token-value---source-env-value---entry-uid-value---include-variants)
-* [`csdx cm:entries:publish-modified [-a <value>] [--retry-failed <value>] [--bulk-publish <value>] [--source-env <value>] [--content-types <value>] [--locales <value>] [-e <value>] [-c <value>] [-y] [--branch <value>]`](#csdx-cmentriespublish-modified--a-value---retry-failed-value---bulk-publish-value---source-env-value---content-types-value---locales-value--e-value--c-value--y---branch-value)
-* [`csdx cm:entries:publish-non-localized-fields [-a <value>] [--retry-failed <value>] [--bulk-publish <value>] [--source-env <value>] [--content-types <value>] [-e <value>] [-c <value>] [-y] [--branch <value>]`](#csdx-cmentriespublish-non-localized-fields--a-value---retry-failed-value---bulk-publish-value---source-env-value---content-types-value--e-value--c-value--y---branch-value)
-* [`csdx cm:entries:publish-only-unpublished [-a <value>] [--retry-failed <value>] [--bulk-publish <value>] [--source-env <value>] [--content-types <value>] [--locales <value>] [-e <value>] [-c <value>] [-y] [--branch <value>]`](#csdx-cmentriespublish-only-unpublished--a-value---retry-failed-value---bulk-publish-value---source-env-value---content-types-value---locales-value--e-value--c-value--y---branch-value)
-* [`csdx cm:entries:unpublish`](#csdx-cmentriesunpublish)
-* [`csdx cm:entries:update-and-publish [-a <value>] [--retry-failed <value>] [--bulk-publish <value>] [--content-types <value>] [-t <value>] [-e <value>] [-c <value>] [-y] [--locales <value>] [--branch <value>]`](#csdx-cmentriesupdate-and-publish--a-value---retry-failed-value---bulk-publish-value---content-types-value--t-value--e-value--c-value--y---locales-value---branch-value)
-* [`csdx cm:stacks:export [-c <value>] [-k <value>] [-d <value>] [-a <value>] [--module <value>] [--content-types <value>] [--branch <value>] [--secured-assets]`](#csdx-cmstacksexport--c-value--k-value--d-value--a-value---module-value---content-types-value---branch-value---secured-assets)
-* [`csdx cm:export-to-csv`](#csdx-cmexport-to-csv)
-* [`csdx cm:stacks:import [-c <value>] [-k <value>] [-d <value>] [-a <value>] [--module <value>] [--backup-dir <value>] [--branch <value>] [--import-webhook-status disable|current]`](#csdx-cmstacksimport--c-value--k-value--d-value--a-value---module-value---backup-dir-value---branch-value---import-webhook-status-disablecurrent)
-* [`csdx cm:stacks:import-setup [-k <value>] [-d <value>] [-a <value>] [--modules <value,value>]`](#csdx-cmstacksimport-setup--k-value--d-value--a-value---modules-valuevalue)
-* [`csdx cm:stacks:migration [-k <value>] [-a <value>] [--file-path <value>] [--branch <value>] [--config-file <value>] [--config <value>] [--multiple]`](#csdx-cmstacksmigration--k-value--a-value---file-path-value---branch-value---config-file-value---config-value---multiple)
-* [`csdx cm:stacks:seed [--repo <value>] [--org <value>] [-k <value>] [-n <value>] [-y] [-s <value>] [--locale <value>]`](#csdx-cmstacksseed---repo-value---org-value--k-value--n-value--y--s-value---locale-value)
-* [`csdx cm:stacks:clone [--source-branch <value>] [--target-branch <value>] [--source-management-token-alias <value>] [--destination-management-token-alias <value>] [-n <value>] [--type a|b] [--source-stack-api-key <value>] [--destination-stack-api-key <value>] [--import-webhook-status disable|current]`](#csdx-cmstacksclone---source-branch-value---target-branch-value---source-management-token-alias-value---destination-management-token-alias-value--n-value---type-ab---source-stack-api-key-value---destination-stack-api-key-value---import-webhook-status-disablecurrent)
-* [`csdx cm:stacks:audit`](#csdx-cmstacksaudit)
-* [`csdx cm:stacks:audit:fix`](#csdx-cmstacksauditfix)
-* [`csdx cm:stacks:clone [--source-branch <value>] [--target-branch <value>] [--source-management-token-alias <value>] [--destination-management-token-alias <value>] [-n <value>] [--type a|b] [--source-stack-api-key <value>] [--destination-stack-api-key <value>] [--import-webhook-status disable|current]`](#csdx-cmstacksclone---source-branch-value---target-branch-value---source-management-token-alias-value---destination-management-token-alias-value--n-value---type-ab---source-stack-api-key-value---destination-stack-api-key-value---import-webhook-status-disablecurrent)
-* [`csdx cm:stacks:export [-c <value>] [-k <value>] [-d <value>] [-a <value>] [--module <value>] [--content-types <value>] [--branch <value>] [--secured-assets]`](#csdx-cmstacksexport--c-value--k-value--d-value--a-value---module-value---content-types-value---branch-value---secured-assets)
-* [`csdx cm:stacks:import [-c <value>] [-k <value>] [-d <value>] [-a <value>] [--module <value>] [--backup-dir <value>] [--branch <value>] [--import-webhook-status disable|current]`](#csdx-cmstacksimport--c-value--k-value--d-value--a-value---module-value---backup-dir-value---branch-value---import-webhook-status-disablecurrent)
-* [`csdx cm:stacks:import-setup [-k <value>] [-d <value>] [-a <value>] [--modules <value,value>]`](#csdx-cmstacksimport-setup--k-value--d-value--a-value---modules-valuevalue)
-* [`csdx cm:stacks:migration [-k <value>] [-a <value>] [--file-path <value>] [--branch <value>] [--config-file <value>] [--config <value>] [--multiple]`](#csdx-cmstacksmigration--k-value--a-value---file-path-value---branch-value---config-file-value---config-value---multiple)
-* [`csdx cm:stacks:publish`](#csdx-cmstackspublish)
-* [`csdx cm:stacks:publish-clear-logs`](#csdx-cmstackspublish-clear-logs)
-* [`csdx cm:stacks:publish-configure`](#csdx-cmstackspublish-configure)
-* [`csdx cm:stacks:publish-revert`](#csdx-cmstackspublish-revert)
-* [`csdx cm:stacks:seed [--repo <value>] [--org <value>] [-k <value>] [-n <value>] [-y] [-s <value>] [--locale <value>]`](#csdx-cmstacksseed---repo-value---org-value--k-value--n-value--y--s-value---locale-value)
-* [`csdx csdx cm:stacks:unpublish [-a <value>] [-e <value>] [-c <value>] [-y] [--locale <value>] [--branch <value>] [--retry-failed <value>] [--bulk-unpublish <value>] [--content-type <value>] [--delivery-token <value>] [--only-assets] [--only-entries]`](#csdx-csdx-cmstacksunpublish--a-value--e-value--c-value--y---locale-value---branch-value---retry-failed-value---bulk-unpublish-value---content-type-value---delivery-token-value---only-assets---only-entries)
-* [`csdx config:get:base-branch`](#csdx-configgetbase-branch)
-* [`csdx config:get:ea-header`](#csdx-configgetea-header)
-* [`csdx config:get:early-access-header`](#csdx-configgetearly-access-header)
-* [`csdx config:get:log`](#csdx-configgetlog)
-* [`csdx config:get:proxy`](#csdx-configgetproxy)
-* [`csdx config:get:rate-limit`](#csdx-configgetrate-limit)
-* [`csdx config:get:region`](#csdx-configgetregion)
-* [`csdx config:remove:base-branch`](#csdx-configremovebase-branch)
-* [`csdx config:remove:ea-header`](#csdx-configremoveea-header)
-* [`csdx config:remove:early-access-header`](#csdx-configremoveearly-access-header)
-* [`csdx config:remove:proxy`](#csdx-configremoveproxy)
-* [`csdx config:remove:rate-limit`](#csdx-configremoverate-limit)
-* [`csdx config:set:base-branch`](#csdx-configsetbase-branch)
-* [`csdx config:set:ea-header`](#csdx-configsetea-header)
-* [`csdx config:set:early-access-header`](#csdx-configsetearly-access-header)
-* [`csdx config:set:log`](#csdx-configsetlog)
-* [`csdx config:set:proxy`](#csdx-configsetproxy)
-* [`csdx config:set:rate-limit`](#csdx-configsetrate-limit)
-* [`csdx config:set:region [REGION]`](#csdx-configsetregion-region)
-* [`csdx help [COMMAND]`](#csdx-help-command)
-* [`csdx launch`](#csdx-launch)
-* [`csdx launch:deployments`](#csdx-launchdeployments)
-* [`csdx launch:environments`](#csdx-launchenvironments)
-* [`csdx launch:functions`](#csdx-launchfunctions)
-* [`csdx launch:logs`](#csdx-launchlogs)
-* [`csdx launch:open`](#csdx-launchopen)
-* [`csdx launch:rollback`](#csdx-launchrollback)
-* [`csdx login`](#csdx-login)
-* [`csdx logout`](#csdx-logout)
-* [`csdx plugins`](#csdx-plugins)
-* [`csdx plugins:add PLUGIN`](#csdx-pluginsadd-plugin)
-* [`csdx plugins:inspect PLUGIN...`](#csdx-pluginsinspect-plugin)
-* [`csdx plugins:install PLUGIN`](#csdx-pluginsinstall-plugin)
-* [`csdx plugins:link PATH`](#csdx-pluginslink-path)
-* [`csdx plugins:remove [PLUGIN]`](#csdx-pluginsremove-plugin)
-* [`csdx plugins:reset`](#csdx-pluginsreset)
-* [`csdx plugins:uninstall [PLUGIN]`](#csdx-pluginsuninstall-plugin)
-* [`csdx plugins:unlink [PLUGIN]`](#csdx-pluginsunlink-plugin)
-* [`csdx plugins:update`](#csdx-pluginsupdate)
-* [`csdx tokens`](#csdx-tokens)
-* [`csdx whoami`](#csdx-whoami)
-
-## `csdx audit`
-
-Perform audits and find possible errors in the exported Contentstack data
-
-```
-USAGE
-  $ csdx audit [-c <value>] [-d <value>] [--show-console-output] [--report-path <value>] [--modules
-    content-types|global-fields|entries|extensions|workflows|custom-roles|assets|field-rules|composable-studio...]
-    [--columns <value>] [--sort <value>] [--filter <value>] [--csv] [--no-truncate] [--no-header] [--output
-    csv|json|yaml]
-
-FLAGS
-  --modules=<option>...  Provide the list of modules to be audited
-                         <options: content-types|global-fields|entries|extensions|workflows|custom-roles|assets|field-ru
-                         les|composable-studio>
-  --report-path=<value>  Path to store the audit reports
-
-COMMON FLAGS
-  -c, --config=<value>       Path of the external config
-  -d, --data-dir=<value>     Path where the data is stored
-      --show-console-output  Display the audit and audit fix result for individual modules
-
-TABLE FLAGS
-  --columns=<value>  Specify columns to display, comma-separated.
-  --csv              Output results in CSV format.
-  --filter=<value>   Filter rows by a column value (e.g., name=foo).
-  --no-header        Hide table headers in output.
-  --no-truncate      Prevent truncation of long text in columns.
-  --output=<option>  Specify output format: csv, json, or yaml.
-                     <options: csv|json|yaml>
-  --sort=<value>     Sort the table by a column. Use "-" for descending.
-
-DESCRIPTION
-  Perform audits and find possible errors in the exported Contentstack data
-
-ALIASES
-  $ csdx audit
-  $ csdx cm:stacks:audit
-
-EXAMPLES
-  $ csdx audit
-
-  $ csdx audit --report-path=<path>
-
-  $ csdx audit --report-path=<path> --csv
-
-  $ csdx audit --report-path=<path> --filter="name=<filter-value>"
-
-  $ csdx audit --report-path=<path> --modules=content-types --filter="name="<filter-value>"
-```
-
-## `csdx audit:fix`
-
-Perform audits and fix possible errors in the exported Contentstack data.
-
-```
-USAGE
-  $ csdx audit:fix [-c <value>] [-d <value>] [--show-console-output] [--report-path <value>] [--modules
-    content-types|global-fields|entries|extensions|workflows|custom-roles|assets|field-rules|composable-studio...]
-    [--copy-path <value> --copy-dir] [--fix-only
-    reference|global_field|json:rte|json:extension|blocks|group|content_types...] [--columns <value>] [--sort <value>]
-    [--filter <value>] [--csv] [--no-truncate] [--no-header] [--output csv|json|yaml]
-
-FLAGS
-  --copy-dir              Create backup from the original data.
-  --copy-path=<value>     Provide the path to backup the copied data
-  --fix-only=<option>...  Provide the list of fix options
-                          <options: reference|global_field|json:rte|json:extension|blocks|group|content_types>
-  --modules=<option>...   Provide the list of modules to be audited
-                          <options: content-types|global-fields|entries|extensions|workflows|custom-roles|assets|field-r
-                          ules|composable-studio>
-  --report-path=<value>   Path to store the audit reports
-
-COMMON FLAGS
-  -c, --config=<value>       Path of the external config
-  -d, --data-dir=<value>     Path where the data is stored
-      --show-console-output  Display the audit and audit fix result for individual modules
-
-TABLE FLAGS
-  --columns=<value>  Specify columns to display, comma-separated.
-  --csv              Output results in CSV format.
-  --filter=<value>   Filter rows by a column value (e.g., name=foo).
-  --no-header        Hide table headers in output.
-  --no-truncate      Prevent truncation of long text in columns.
-  --output=<option>  Specify output format: csv, json, or yaml.
-                     <options: csv|json|yaml>
-  --sort=<value>     Sort the table by a column. Use "-" for descending.
-
-DESCRIPTION
-  Perform audits and fix possible errors in the exported Contentstack data.
-
-ALIASES
-  $ csdx audit:fix
-  $ csdx cm:stacks:audit:fix
-
-EXAMPLES
-  $ csdx audit:fix --copy-dir
-
-  $ csdx audit:fix --report-path=<path> --copy-dir
-
-  $ csdx audit:fix --report-path=<path> --copy-dir --csv
-
-  $ csdx audit:fix --fix-only=reference,global_field --copy-dir
-
-  $ csdx audit:fix --report-path=<path> --filter="name=<filter-value>"
-
-  $ csdx audit:fix --report-path=<path> --modules=content-types --filter="name="<filter-value>" --copy-dir --copy-path=<path>
-```
-
-## `csdx auth:login`
-
-User sessions login
-
-```
-USAGE
-  $ csdx auth:login [-u <value> | --oauth] [-p <value> | ]
-
-FLAGS
-  -p, --password=<value>  Password of your Contentstack app.
-  -u, --username=<value>  Email address of your Contentstack account.
-      --oauth             Enables single sign-on (SSO) in Contentstack CLI.
-
-DESCRIPTION
-  User sessions login
-
-ALIASES
-  $ csdx login
-
-EXAMPLES
-  $ csdx auth:login
-
-  $ csdx auth:login -u <username>
-
-  $ csdx auth:login -u <username> -p <password>
-
-  $ csdx auth:login --username <username>
-
-  $ csdx auth:login --username <username> --password <password>
-```
-
-_See code: [@contentstack/cli-auth](https://github.com/contentstack/cli/blob/main/packages/contentstack-auth/src/commands/auth/login.ts)_
-
-## `csdx auth:logout`
-
-User session logout
-
-```
-USAGE
-  $ csdx auth:logout [-y]
-
-FLAGS
-  -y, --yes  Force log out by skipping the confirmation.
-
-DESCRIPTION
-  User session logout
-
-ALIASES
-  $ csdx logout
-
-EXAMPLES
-  $ csdx auth:logout
-
-  $ csdx auth:logout -y
-
-  $ csdx auth:logout --yes
-```
-
-_See code: [@contentstack/cli-auth](https://github.com/contentstack/cli/blob/main/packages/contentstack-auth/src/commands/auth/logout.ts)_
-
-## `csdx auth:tokens`
-
-Lists all existing tokens added to the session
-
-```
-USAGE
-  $ csdx auth:tokens [--columns <value>] [--sort <value>] [--filter <value>] [--csv] [--no-truncate]
-    [--no-header] [--output csv|json|yaml]
-
-TABLE FLAGS
-  --columns=<value>  Specify columns to display, comma-separated.
-  --csv              Output results in CSV format.
-  --filter=<value>   Filter rows by a column value (e.g., name=foo).
-  --no-header        Hide table headers in output.
-  --no-truncate      Prevent truncation of long text in columns.
-  --output=<option>  Specify output format: csv, json, or yaml.
-                     <options: csv|json|yaml>
-  --sort=<value>     Sort the table by a column. Use "-" for descending.
-
-DESCRIPTION
-  Lists all existing tokens added to the session
-
-ALIASES
-  $ csdx tokens
-
-EXAMPLES
-  $ csdx auth:tokens
-```
-
-_See code: [@contentstack/cli-auth](https://github.com/contentstack/cli/blob/main/packages/contentstack-auth/src/commands/auth/tokens/index.ts)_
-
-## `csdx auth:tokens:add [-a <value>] [--delivery] [--management] [-e <value>] [-k <value>] [-y] [--token <value>]`
-
-Adds management/delivery tokens to your session to use it with other CLI commands
-
-```
-USAGE
-  $ csdx auth:tokens:add [-a <value>] [--delivery] [--management] [-e <value>] [-k <value>] [-y] [--token <value>]
-
-FLAGS
-  -a, --alias=<value>          Alias (name) you want to assign to the token
-  -d, --delivery               Set this flag to save delivery token
-  -e, --environment=<value>    Environment name for delivery token
-  -k, --stack-api-key=<value>  Stack API Key
-  -m, --management             Set this flag to save management token
-  -t, --token=<value>          [env: TOKEN] Add the token name
-  -y, --yes                    Use this flag to skip confirmation
-
-DESCRIPTION
-  Adds management/delivery tokens to your session to use it with other CLI commands
-
-EXAMPLES
-  $ csdx auth:tokens:add
-
-  $ csdx auth:tokens:add -a <alias>
-
-  $ csdx auth:tokens:add -k <stack api key>
-
-  $ csdx auth:tokens:add --delivery
-
-  $ csdx auth:tokens:add --management
-
-  $ csdx auth:tokens:add -e <environment>
-
-  $ csdx auth:tokens:add --token <token>
-
-  $ csdx auth:tokens:add -a <alias> -k <stack api key> --management --token <management token>
-
-  $ csdx auth:tokens:add -a <alias> -k <stack api key> --delivery -e <environment> --token <delivery token>
-
-  $ csdx auth:tokens:add --alias <alias> --stack-api-key <stack api key> --management --token <management token>
-
-  $ csdx auth:tokens:add --alias <alias> --stack-api-key <stack api key> --delivery -e <environment> --token <delivery token>
-```
-
-_See code: [@contentstack/cli-auth](https://github.com/contentstack/cli/blob/main/packages/contentstack-auth/src/commands/auth/tokens/add.ts)_
-
-## `csdx auth:tokens:remove`
-
-Removes selected tokens
-
-```
-USAGE
-  $ csdx auth:tokens:remove [-a <value>] [-i]
-
-FLAGS
-  -a, --alias=<value>  Alias (name) of the token to delete.
-  -i, --ignore         Ignores if the token is not present.
-
-DESCRIPTION
-  Removes selected tokens
-
-EXAMPLES
-  $ csdx auth:tokens:remove
-
-  $ csdx auth:tokens:remove -a <alias>
-```
-
-_See code: [@contentstack/cli-auth](https://github.com/contentstack/cli/blob/main/packages/contentstack-auth/src/commands/auth/tokens/remove.ts)_
-
-## `csdx auth:whoami`
-
-Display current users email address
-
-```
-USAGE
-  $ csdx auth:whoami
-
-DESCRIPTION
-  Display current users email address
-
-ALIASES
-  $ csdx whoami
-
-EXAMPLES
-  $ csdx auth:whoami
-```
-
-_See code: [@contentstack/cli-auth](https://github.com/contentstack/cli/blob/main/packages/contentstack-auth/src/commands/auth/whoami.ts)_
-
-## `csdx cm:assets:publish [-a <value>] [--retry-failed <value>] [-e <value>] [--folder-uid <value>] [--backup-dir <value>] [--bulk-publish <value>] [-c <value>] [-y] [--locales <value>] [--branch <value>] [--delivery-token <value>] [--source-env <value>]`
-
-Publish assets to the specified environments
-
-```
-USAGE
-  $ csdx cm:assets:publish [-a <value>] [--retry-failed <value>] [-e <value>] [--folder-uid <value>] [--backup-dir
-    <value>] [--bulk-publish <value>] [-c <value>] [-y] [--locales <value>] [--branch <value>] [--delivery-token
-    <value>] [--source-env <value>]
-
-FLAGS
-  -B, --branch=<value>           [default: main] The name of the branch where you want to perform the bulk publish
-                                 operation. If you don’t mention the branch name, then by default the assets from the
-                                 main branch will be published.
-  -a, --alias=<value>            Alias (name) for the management token. You must use either the --alias flag or the
-                                 --stack-api-key flag.
-  -c, --config=<value>           (optional) The path of the optional configuration JSON file containing all the options
-                                 for a single run. Refer to the configure command to create a configuration file.
-  -e, --environments=<value>...  The name of the environment on which entries will be published. In case of multiple
-                                 environments, specify their names separated by spaces.
-  -k, --stack-api-key=<value>    API key of the source stack. You must use either the --stack-api-key flag or the
-                                 --alias flag.
-  -l, --locales=<value>...       Locales in which assets will be published, e.g., en-us. In the case of multiple
-                                 locales, specify the codes separated by spaces.
-  -y, --yes                      Set it to true to process the command with the current configuration.
-      --api-version=<value>      API version to be used. Values [Default: 3, Nested Reference Publishing: 3.2].
-      --backup-dir=<value>       (optional) Path to the import backup directory. When set, each imported asset is
-                                 published only to the environments and locales it was published to in the source stack
-                                 (read from the backup’s publish details and asset UID mapping), with asset-scan gating
-                                 applied. Intended for the post-import publish flow.
-      --bulk-publish=<value>     [default: true] Set this flag to use Contentstack’s Bulk Publish APIs. It is true, by
-                                 default.
-      --delivery-token=<value>   The delivery token of the source environment.
-      --folder-uid=<value>       (optional) The UID of the Assets’ folder from which the assets need to be published.
-                                 The default value is cs_root.
-      --retry-failed=<value>     Use this option to retry publishing the failed assets from the logfile. Specify the
-                                 name of the logfile that lists failed publish calls. If this option is used, it will
-                                 override all other flags.
-      --source-env=<value>       Source environment
-
-DESCRIPTION
-  Publish assets to the specified environments
-  The assets command is used to publish assets from the specified stack, to the specified environments
-
-  Note: Environment(s) and Locale(s) are required to execute the command successfully
-  But, if retryFailed flag is set, then only a logfile is required
-
-
-ALIASES
-  $ csdx cm:bulk-publish:assets
-
-EXAMPLES
-  General Usage
-
-  $ csdx cm:assets:publish --environments [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE] --alias [MANAGEMENT TOKEN ALIAS]
-
-
-
-  Using --config or -c flag
-
-  Generate a config file at the current working directory using `csdx cm:stacks:publish-configure -a [ALIAS]`
-
-  $ csdx cm:assets:publish --config [PATH TO CONFIG FILE]
-
-  $ csdx cm:assets:publish -c [PATH TO CONFIG FILE]
-
-
-
-  Using --retry-failed flag
-
-  $ csdx cm:assets:publish --retry-failed [LOG FILE NAME]
-
-
-
-  Using --branch flag
-
-  $ csdx cm:assets:publish --environments [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE] --alias [MANAGEMENT TOKEN ALIAS] --branch [BRANCH NAME]
-
-
-
-  Using --source-env
-
-  $ csdx cm:assets:publish --environments [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE] --alias [MANAGEMENT TOKEN ALIAS] --source-env [SOURCE ENVIRONMENT] --delivery-token [DELIVERY TOKEN]
-
-
-
-  Using --stack-api-key flag
-
-  $ csdx cm:assets:publish --environments [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE] --stack-api-key [STACK API KEY]
-
-
-
-  Using --backup-dir flag (publish imported assets to their original environments after asset scanning)
-
-  $ csdx cm:assets:publish --backup-dir [PATH TO IMPORT BACKUP DIR] --stack-api-key [STACK API KEY]
-```
-
-_See code: [@contentstack/cli-cm-bulk-publish](https://github.com/contentstack/cli/blob/main/packages/contentstack-bulk-publish/src/commands/cm/assets/publish.js)_
-
-## `csdx cm:assets:unpublish`
-
-Unpublish assets from given environment
-
-```
-USAGE
-  $ csdx cm:assets:unpublish [-a <value>] [-k <value>] [-e <value>] [-c <value>] [-y] [--locale <value>] [--branch
-    <value>] [--retry-failed <value>] [--bulk-unpublish <value>] [--api-version <value>] [--delivery-token <value>]
-
-FLAGS
-  -a, --alias=<value>           Alias (name) of the management token. You must use either the --alias flag or the
-                                --stack-api-key flag.
-  -c, --config=<value>          (optional) Path of an optional configuration JSON file containing all the options for a
-                                single run. Refer to the configure command to create a configuration file.
-  -e, --environment=<value>     The name of the environment from where entries/assets need to be unpublished.
-  -k, --stack-api-key=<value>   API key of the source stack. You must use either the --stack-api-key flag or the --alias
-                                flag.
-  -y, --yes                     Set it to true to process the command with the current configuration.
-      --api-version=<value>     API version to be used. Values [Default: 3, Nested Reference Publishing: 3.2].
-      --branch=<value>          [default: main] The name of the branch where you want to perform the bulk unpublish
-                                operation. If you don’t mention the branch name, then by default the content from the
-                                main branch will be unpublished.
-      --bulk-unpublish=<value>  [default: true] Set this flag to use Contentstack’s Bulk Publish APIs. It is true, by
-                                default.
-      --delivery-token=<value>  The delivery token of the source environment.
-      --locale=<value>          Locale from which entries/assets will be unpublished, e.g., en-us.
-      --retry-failed=<value>    (optional) Use this option to retry unpublishing the failed entries from the logfile.
-                                Specify the name of the logfile that lists failed unpublish calls. If this option is
-                                used, it will override all other flags.
-
-DESCRIPTION
-  Unpublish assets from given environment
-  The unpublish command is used for unpublishing assets from the given environment
-
-  Note: Environment (Source Environment) and Locale are required to execute the command successfully
-  But, if retry-failed flag is set, then only a logfile is required
-
-EXAMPLES
-  General Usage
-
-  $ csdx cm:assets:unpublish --bulk-unpublish --environment [SOURCE ENV] --locale [LOCALE] --alias [MANAGEMENT TOKEN ALIAS] --delivery-token [DELIVERY TOKEN]
-
-
-
-  Using --config or -c flag
-
-  Generate a config file at the current working directory using `csdx cm:bulk-publish:configure --alias [ALIAS]`
-
-  $ csdx cm:assets:unpublish --config [PATH TO CONFIG FILE]
-
-  $ csdx cm:assets:unpublish -c [PATH TO CONFIG FILE]
-
-
-
-  Using --retry-failed flag
-
-  $ csdx cm:assets:unpublish --retry-failed [LOG FILE NAME]
-
-
-
-  Using --branch flag
-
-  $ csdx cm:assets:unpublish --bulk-unpublish --environment [SOURCE ENV] --locale [LOCALE] --alias [MANAGEMENT TOKEN ALIAS] --delivery-token [DELIVERY TOKEN] --branch [BRANCH NAME]
-
-
-
-  Using --stack-api-key flag
-
-  $ csdx cm:assets:unpublish --bulk-unpublish --environment [SOURCE ENV] --locale [LOCALE] --stack-api-key [STACK API KEY] --delivery-token [DELIVERY TOKEN]
-```
-
-_See code: [@contentstack/cli-cm-bulk-publish](https://github.com/contentstack/cli/blob/main/packages/contentstack-bulk-publish/src/commands/cm/assets/unpublish.js)_
-
-## `csdx cm:bootstrap`
-
-Bootstrap contentstack apps
-
-```
-USAGE
-  $ csdx cm:bootstrap [--app-name <value>] [--project-dir <value>] [-k <value> | --org <value> | -n <value>] [-y]
-    [--run-dev-server] [-a <value>]
-
-FLAGS
-  -a, --alias=<value>          Alias of the management token
-  -k, --stack-api-key=<value>  Provide stack API key to seed content
-  -n, --stack-name=<value>     Name of the new stack that will be created.
-  -y, --yes                    [Optional] Skip stack confirmation
-      --app-name=<value>       App name, kickstart-next, kickstart-next-ssr, kickstart-next-ssg, kickstart-next-graphql,
-                               kickstart-next-middleware, kickstart-nuxt, kickstart-nuxt-ssr
-      --org=<value>            Provide organization UID to create a new stack
-      --project-dir=<value>    Directory to setup the project. If directory name has a space then provide the path as a
-                               string or escap the space using back slash eg: "../../test space" or ../../test\ space
-      --run-dev-server         Automatically start the development server after setup
-
-DESCRIPTION
-  Bootstrap contentstack apps
-
-EXAMPLES
-  $ csdx cm:bootstrap
-
-  $ csdx cm:bootstrap --project-dir <path/to/setup/the/app>
-
-  $ csdx cm:bootstrap --app-name "kickstart-next" --project-dir <path/to/setup/the/app>
-
-  $ csdx cm:bootstrap --app-name "kickstart-next" --project-dir <path/to/setup/the/app> --stack-api-key "stack-api-key"
-
-  $ csdx cm:bootstrap --app-name "kickstart-next" --project-dir <path/to/setup/the/app> --org "your-org-uid" --stack-name "stack-name"
-
-  $ csdx cm:bootstrap --app-name "kickstart-next" --project-dir <path/to/setup/the/app> --run-dev-server
-```
-
-_See code: [@contentstack/cli-cm-bootstrap](https://github.com/contentstack/cli/blob/main/packages/contentstack-bootstrap/src/commands/cm/bootstrap.ts)_
-
-## `csdx cm:branches`
-
-List the branches
-
-```
-USAGE
-  $ csdx cm:branches
-
-FLAGS
-  -k, --stack-api-key=<value>  Stack API key
-      --verbose                Verbose, display information in detailed format.
-
-DESCRIPTION
-  List the branches
-
-EXAMPLES
-  $ csdx cm:branches
-
-  $ csdx cm:branches --verbose
-
-  $ csdx cm:branches -k <stack api key>
-```
-
-_See code: [@contentstack/cli-cm-branches](https://github.com/contentstack/cli/blob/main/packages/contentstack-export/src/commands/cm/branches/index.ts)_
-
-## `csdx cm:branches:create`
-
-Create a new branch
-
-```
-USAGE
-  $ csdx cm:branches:create
-  $ csdx cm:branches:create [--source <value>] [--uid <value>] [-k <value>]
-  $ csdx cm:branches:create [--source <value>] [--uid <value>] [--stack-api-key <value>]
-
-FLAGS
-  -k, --stack-api-key=<value>  Stack API key
-      --source=<value>         Source branch from which a new branch is to be created.
-      --uid=<value>            Branch UID (unique name) to be created.
-
-DESCRIPTION
-  Create a new branch
-
-EXAMPLES
-  $ csdx cm:branches:create
-
-  $ csdx cm:branches:create --source main -uid new_branch -k bltxxxxxxxx
-
-  $ csdx cm:branches:create --source main --uid new_branch --stack-api-key bltxxxxxxxx
-```
-
-_See code: [@contentstack/cli-cm-branches](https://github.com/contentstack/cli/blob/main/packages/contentstack-export/src/commands/cm/branches/create.ts)_
-
-## `csdx cm:branches:delete [-uid <value>] [-k <value>]`
-
-Delete a branch
-
-```
-USAGE
-  $ csdx cm:branches:delete [-uid <value>] [-k <value>]
-  $ csdx cm:branches:delete [--uid <value>] [--stack-api-key <value>]
-
-FLAGS
-  -k, --stack-api-key=<value>  Stack API key
-  -y, --yes                    Force the deletion of the branch by skipping the confirmation
-      --uid=<value>            Branch UID to be deleted
-
-DESCRIPTION
-  Delete a branch
-
-EXAMPLES
-  $ csdx cm:branches:delete
-
-  $ csdx cm:branches:delete --uid main -k bltxxxxxxxx
-
-  $ csdx cm:branches:delete --uid main --stack-api-key bltxxxxxxxx
-
-  $ csdx cm:branches:delete --uid main --stack-api-key bltxxxxxxxx --yes
-```
-
-_See code: [@contentstack/cli-cm-branches](https://github.com/contentstack/cli/blob/main/packages/contentstack-export/src/commands/cm/branches/delete.ts)_
-
-## `csdx cm:branches:diff [--base-branch <value>] [--compare-branch <value>] [-k <value>][--module <value>] [--format <value>] [--csv-path <value>]`
-
-Differences between two branches
-
-```
-USAGE
-  $ csdx cm:branches:diff [--base-branch <value>] [--compare-branch <value>] [-k <value>][--module <value>] [--format
-    <value>] [--csv-path <value>]
-
-FLAGS
-  -k, --stack-api-key=<value>   [optional] Provide the stack API key to show the difference between branches.
-      --base-branch=<value>     [optional] Base branch (Target branch).
-      --compare-branch=<value>  [optional] Compare branch (Source branch).
-      --csv-path=<value>        [optional] Custom path for CSV output file. If not provided, will use the current
-                                working directory.
-      --format=<option>         [default: compact-text] [default: compact-text] [optional] Type of flags to show the
-                                difference between two branches. <options: compact-text, detailed-text>
-                                <options: compact-text|detailed-text>
-      --module=<option>         [optional] Module. <options: content-types, global-fields, all>
-                                <options: content-types|global-fields|all>
-
-DESCRIPTION
-  Differences between two branches
-
-EXAMPLES
-  $ csdx cm:branches:diff
-
-  $ csdx cm:branches:diff --stack-api-key "bltxxxxxxxx"
-
-  $ csdx cm:branches:diff --compare-branch "develop"
-
-  $ csdx cm:branches:diff --compare-branch "develop" --stack-api-key "bltxxxxxxxx"
-
-  $ csdx cm:branches:diff --compare-branch "develop" --module "content-types"
-
-  $ csdx cm:branches:diff --module "content-types" --format "detailed-text"
-
-  $ csdx cm:branches:diff --compare-branch "develop" --format "detailed-text"
-
-  $ csdx cm:branches:diff --stack-api-key "bltxxxxxxxx" --base-branch "main"
-
-  $ csdx cm:branches:diff --stack-api-key "bltxxxxxxxx" --base-branch "main" --compare-branch "develop"
-
-  $ csdx cm:branches:diff --stack-api-key "bltxxxxxxxx" --base-branch "main" --module "content-types"
-
-  $ csdx cm:branches:diff --stack-api-key "bltxxxxxxxx" --base-branch "main" --compare-branch "develop" --module "content-types"
-
-  $ csdx cm:branches:diff --stack-api-key "bltxxxxxxxx" --base-branch "main" --compare-branch "develop" --module "content-types" --format "detailed-text"
-
-  $ csdx cm:branches:diff --stack-api-key "bltxxxxxxxx" --base-branch "main" --compare-branch "develop" --module "content-types" --format "compact-text"
-
-  $ csdx cm:branches:diff --stack-api-key "bltxxxxxxxx" --base-branch "main" --compare-branch "develop" --module "content-types" --format "detailed-text" --csv-path "./reports/diff-report.csv"
-```
-
-_See code: [@contentstack/cli-cm-branches](https://github.com/contentstack/cli/blob/main/packages/contentstack-export/src/commands/cm/branches/diff.ts)_
-
-## `csdx cm:branches:merge [-k <value>][--compare-branch <value>] [--no-revert] [--export-summary-path <value>] [--use-merge-summary <value>] [--comment <value>] [--base-branch <value>]`
-
-Merge changes from a branch
-
-```
-USAGE
-  $ csdx cm:branches:merge [-k <value>][--compare-branch <value>] [--no-revert] [--export-summary-path <value>]
-    [--use-merge-summary <value>] [--comment <value>] [--base-branch <value>]
-
-FLAGS
-  -k, --stack-api-key=<value>        [optional] Provide stack API key to show the difference between the branches.
-      --base-branch=<value>          [optional] Base branch (Target branch).
-      --comment=<value>              [optional] Pass a comment.
-      --compare-branch=<value>       [optional] Compare branch (Source branch).
-      --export-summary-path=<value>  [optional] Export summary file path.
-      --no-revert                    [optional] If passed, will not create the new revert branch.
-      --use-merge-summary=<value>    [optional] Path of merge summary file.
-
-DESCRIPTION
-  Merge changes from a branch
-
-EXAMPLES
-  $ csdx cm:branches:merge --stack-api-key bltxxxxxxxx --compare-branch feature-branch
-
-  $ csdx cm:branches:merge --stack-api-key bltxxxxxxxx --comment "merge comment"
-
-  $ csdx cm:branches:merge -k bltxxxxxxxx --base-branch base-branch
-
-  $ csdx cm:branches:merge --export-summary-path file/path
-
-  $ csdx cm:branches:merge --use-merge-summary file-path
-
-  $ csdx cm:branches:merge -k bltxxxxxxxx --no-revert
-
-  $ csdx cm:branches:merge -k bltxxxxxxxx --compare-branch feature-branch --no-revert
-```
-
-_See code: [@contentstack/cli-cm-branches](https://github.com/contentstack/cli/blob/main/packages/contentstack-export/src/commands/cm/branches/merge.ts)_
-
-## `csdx cm:branches:merge-status -k <value> --merge-uid <value>`
-
-Check the status of a branch merge job
-
-```
-USAGE
-  $ csdx cm:branches:merge-status -k <value> --merge-uid <value>
-
-FLAGS
-  -k, --stack-api-key=<value>  (required) Provide your stack API key.
-      --merge-uid=<value>      (required) Merge job UID to check status for.
-
-DESCRIPTION
-  Check the status of a branch merge job
-
-EXAMPLES
-  $ csdx cm:branches:merge-status -k bltxxxxxxxx --merge-uid merge_abc123
-
-  $ csdx cm:branches:merge-status --stack-api-key bltxxxxxxxx --merge-uid merge_abc123
-```
-
-_See code: [@contentstack/cli-cm-branches](https://github.com/contentstack/cli/blob/main/packages/contentstack-export/src/commands/cm/branches/merge-status.ts)_
-
-## `csdx cm:bulk-publish`
-
-Bulk Publish script for managing entries and assets
-
-```
-USAGE
-  $ csdx cm:bulk-publish
-
-DESCRIPTION
-  Bulk Publish script for managing entries and assets
-```
-
-_See code: [@contentstack/cli-cm-bulk-publish](https://github.com/contentstack/cli/blob/main/packages/contentstack-bulk-publish/src/commands/cm/bulk-publish/index.js)_
-
-## `csdx cm:entries:update-and-publish [-a <value>] [--retry-failed <value>] [--bulk-publish <value>] [--content-types <value>] [-t <value>] [-e <value>] [-c <value>] [-y] [--locales <value>] [--branch <value>]`
-
-Add fields from updated content types to their respective entries
-
-```
-USAGE
-  $ csdx cm:bulk-publish:add-fields cm:entries:update-and-publish [-a <value>] [--retry-failed <value>] [--bulk-publish <value>]
-    [--content-types <value>] [-t <value>] [-e <value>] [-c <value>] [-y] [--locales <value>] [--branch <value>]
-
-FLAGS
-  -B, --branch=<value>            [default: main] The name of the branch where you want to perform the bulk publish
-                                  operation. If you don’t mention the branch name, then by default the content from the
-                                  main branch will be published.
-  -a, --alias=<value>             Alias (name) of the management token. You must use either the --alias flag or the
-                                  --stack-api-key flag.
-  -c, --config=<value>            (optional) The path of the optional configuration JSON file containing all the options
-                                  for a single run. Refer to the configure command to create a configuration file.
-  -e, --environments=<value>...   The name of the environment on which entries will be published. In case of multiple
-                                  environments, specify their names separated by spaces.
-  -k, --stack-api-key=<value>     API key of the source stack. You must use either the --stack-api-key flag or the
-                                  --alias flag.
-  -l, --locales=<value>...        Locales in which entries will be published, e.g., en-us. In the case of multiple
-                                  locales, specify the codes separated by spaces.
-  -t, --contentTypes=<value>...   The Contenttypes from which entries will be published.
-  -y, --yes                       Set it to true to process the command with the current configuration.
-      --api-version=<value>       API version to be used. Values [Default: 3, Nested Reference Publishing: 3.2].
-      --bulk-publish=<value>      [default: true] Set this flag to use Contentstack’s Bulk Publish APIs. It is true, by
-                                  default.
-      --content-types=<value>...  The UID of the content type ID whose entries you want to publish in bulk. In case of
-                                  multiple content types, specify their IDs separated by spaces.
-      --force                     Update and publish all entries even if no fields have been added.
-      --retry-failed=<value>      Use this option to retry publishing the failed entries from the logfile. Specify the
-                                  name of the logfile that lists failed publish calls. If this option is used, it will
-                                  override all other flags.
-
-DESCRIPTION
-  Add fields from updated content types to their respective entries
-  The update-and-publish command is used to update existing entries with the updated schema of the respective content
-  type
-
-  Note: Content types, Environments and Locales are required to execute the command successfully
-  But, if retry-failed flag is set, then only a logfile is required
-
-
-ALIASES
-  $ csdx cm:bulk-publish:add-fields
-
-EXAMPLES
-  General Usage
-
-  $ csdx cm:entries:update-and-publish --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] -a [MANAGEMENT TOKEN ALIAS]
-
-
-
-  Using --config or -c flag
-
-  Generate a config file at the current working directory using `csdx cm:stacks:publish-configure -a [ALIAS]`
-
-  $ csdx cm:entries:update-and-publish --config [PATH TO CONFIG FILE]
-
-  $ csdx cm:entries:update-and-publish -c [PATH TO CONFIG FILE]
-
-
-
-  Using --retry-failed
-
-  $ csdx cm:entries:update-and-publish --retry-failed [LOG FILE NAME]
-
-
-
-  Using --branch
-
-  $ csdx cm:entries:update-and-publish --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] -a [MANAGEMENT TOKEN ALIAS] --branch [BRANCH NAME]
-
-
-
-  Using --stack-api-key
-
-  $ csdx cm:entries:update-and-publish --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] --stack-api-key [STACK API KEY]
-```
-
-## `csdx cm:assets:publish [-a <value>] [--retry-failed <value>] [-e <value>] [--folder-uid <value>] [--backup-dir <value>] [--bulk-publish <value>] [-c <value>] [-y] [--locales <value>] [--branch <value>] [--delivery-token <value>] [--source-env <value>]`
-
-Publish assets to the specified environments
-
-```
-USAGE
-  $ csdx cm:bulk-publish:assets cm:assets:publish [-a <value>] [--retry-failed <value>] [-e <value>] [--folder-uid <value>]
-    [--backup-dir <value>] [--bulk-publish <value>] [-c <value>] [-y] [--locales <value>] [--branch <value>]
-    [--delivery-token <value>] [--source-env <value>]
-
-FLAGS
-  -B, --branch=<value>           [default: main] The name of the branch where you want to perform the bulk publish
-                                 operation. If you don’t mention the branch name, then by default the assets from the
-                                 main branch will be published.
-  -a, --alias=<value>            Alias (name) for the management token. You must use either the --alias flag or the
-                                 --stack-api-key flag.
-  -c, --config=<value>           (optional) The path of the optional configuration JSON file containing all the options
-                                 for a single run. Refer to the configure command to create a configuration file.
-  -e, --environments=<value>...  The name of the environment on which entries will be published. In case of multiple
-                                 environments, specify their names separated by spaces.
-  -k, --stack-api-key=<value>    API key of the source stack. You must use either the --stack-api-key flag or the
-                                 --alias flag.
-  -l, --locales=<value>...       Locales in which assets will be published, e.g., en-us. In the case of multiple
-                                 locales, specify the codes separated by spaces.
-  -y, --yes                      Set it to true to process the command with the current configuration.
-      --api-version=<value>      API version to be used. Values [Default: 3, Nested Reference Publishing: 3.2].
-      --backup-dir=<value>       (optional) Path to the import backup directory. When set, each imported asset is
-                                 published only to the environments and locales it was published to in the source stack
-                                 (read from the backup’s publish details and asset UID mapping), with asset-scan gating
-                                 applied. Intended for the post-import publish flow.
-      --bulk-publish=<value>     [default: true] Set this flag to use Contentstack’s Bulk Publish APIs. It is true, by
-                                 default.
-      --delivery-token=<value>   The delivery token of the source environment.
-      --folder-uid=<value>       (optional) The UID of the Assets’ folder from which the assets need to be published.
-                                 The default value is cs_root.
-      --retry-failed=<value>     Use this option to retry publishing the failed assets from the logfile. Specify the
-                                 name of the logfile that lists failed publish calls. If this option is used, it will
-                                 override all other flags.
-      --source-env=<value>       Source environment
-
-DESCRIPTION
-  Publish assets to the specified environments
-  The assets command is used to publish assets from the specified stack, to the specified environments
-
-  Note: Environment(s) and Locale(s) are required to execute the command successfully
-  But, if retryFailed flag is set, then only a logfile is required
-
-
-ALIASES
-  $ csdx cm:bulk-publish:assets
-
-EXAMPLES
-  General Usage
-
-  $ csdx cm:assets:publish --environments [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE] --alias [MANAGEMENT TOKEN ALIAS]
-
-
-
-  Using --config or -c flag
-
-  Generate a config file at the current working directory using `csdx cm:stacks:publish-configure -a [ALIAS]`
-
-  $ csdx cm:assets:publish --config [PATH TO CONFIG FILE]
-
-  $ csdx cm:assets:publish -c [PATH TO CONFIG FILE]
-
-
-
-  Using --retry-failed flag
-
-  $ csdx cm:assets:publish --retry-failed [LOG FILE NAME]
-
-
-
-  Using --branch flag
-
-  $ csdx cm:assets:publish --environments [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE] --alias [MANAGEMENT TOKEN ALIAS] --branch [BRANCH NAME]
-
-
-
-  Using --source-env
-
-  $ csdx cm:assets:publish --environments [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE] --alias [MANAGEMENT TOKEN ALIAS] --source-env [SOURCE ENVIRONMENT] --delivery-token [DELIVERY TOKEN]
-
-
-
-  Using --stack-api-key flag
-
-  $ csdx cm:assets:publish --environments [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE] --stack-api-key [STACK API KEY]
-
-
-
-  Using --backup-dir flag (publish imported assets to their original environments after asset scanning)
-
-  $ csdx cm:assets:publish --backup-dir [PATH TO IMPORT BACKUP DIR] --stack-api-key [STACK API KEY]
-```
-
-## `csdx cm:bulk-publish:clear`
-
-Clear the log folder
-
-```
-USAGE
-  $ csdx cm:bulk-publish:clear [--log-files-count] [-y]
-
-FLAGS
-  -y, --yes              Delete all files without asking for confirmation
-      --log-files-count  List number of log files
-
-DESCRIPTION
-  Clear the log folder
-
-ALIASES
-  $ csdx cm:bulk-publish:clear
-
-EXAMPLES
-  $ csdx cm:stacks:publish-clear-logs
-
-  $ csdx cm:stacks:publish-clear-logs --log-files-count
-
-  $ csdx cm:stacks:publish-clear-logs --yes
-
-  $ csdx cm:stacks:publish-clear-logs -y
-```
-
-## `csdx cm:bulk-publish:configure`
-
-The configure command is used to generate a configuration file for publish scripts.
-
-```
-USAGE
-  $ csdx cm:bulk-publish:configure [-a <value>] [-k <value>]
-
-FLAGS
-  -a, --alias=<value>          Name (alias) of the management token you want to use. You must use either the --alias
-                               flag or the --stack-api-key flag.
-  -k, --stack-api-key=<value>  API key of the source stack. You must use either the --stack-api-key flag or the --alias
-                               flag.
-
-DESCRIPTION
-  The configure command is used to generate a configuration file for publish scripts.
-
-ALIASES
-  $ csdx cm:bulk-publish:configure
-
-EXAMPLES
-  $ csdx cm:stacks:publish-configure
-
-  $ csdx cm:stacks:publish-configure -a <management_token_alias>
-
-  $ csdx cm:stacks:publish-configure --alias <management_token_alias>
-
-  $ csdx cm:stacks:publish-configure --stack-api-key <stack_api_key>
-```
-
-## `csdx cm:bulk-publish:cross-publish [-a <value>] [--retry-failed <value>] [--bulk-publish <value>] [--content-type <value>] [--locales <value>] [--source-env <value>] [--environments <value>] [--delivery-token <value>] [-c <value>] [-y] [--branch <value>] [--onlyAssets] [--onlyEntries] [--include-variants]`
-
-Publish entries and assets from one environment to other environments
-
-```
-USAGE
-  $ csdx cm:bulk-publish:cross-publish [-a <value>] [--retry-failed <value>] [--bulk-publish <value>] [--content-type <value>]
-    [--locales <value>] [--source-env <value>] [--environments <value>] [--delivery-token <value>] [-c <value>] [-y]
-    [--branch <value>] [--onlyAssets] [--onlyEntries] [--include-variants]
-
-FLAGS
-  -B, --branch=<value>           [default: main] Specify the branch to fetch the content (by default the main branch is
-                                 selected)
-  -a, --alias=<value>            Alias(name) for the management token
-  -c, --config=<value>           Path to the config file
-  -k, --stack-api-key=<value>    Stack API key to be used
-  -y, --yes                      Agree to process the command with the current configuration
-      --api-version=<value>      API version to be used. Values [Default: 3, Nested Reference Publishing: 3.2].
-      --bulk-publish=<value>     [default: true] Set this flag to use Contentstack’s Bulk Publish APIs. It is true, by
-                                 default.
-      --content-type=<value>...  The Contenttypes from which entries will be published
-      --delivery-token=<value>   The delivery token of the source environment.
-      --environments=<value>...  Destination Environments
-      --include-variants         Include Variants flag will publish all associated variant entries.
-      --locales=<value>          Source locale
-      --onlyAssets               Unpublish only assets
-      --onlyEntries              Unpublish only entries
-      --retry-failed=<value>     (optional) Retry publishing failed entries from the logfile (this flag overrides all
-                                 other flags)
-      --source-env=<value>       Source Env
-
-DESCRIPTION
-  Publish entries and assets from one environment to other environments
-  The cross-publish command is used to publish entries and assets from one environment to other environments
-
-  Note: Content Type, Environment, Destination Environment(s) and Locale are required to execute the command
-  successfully
-  But, if retryFailed flag is set, then only a logfile is required
-
-
-EXAMPLES
-  General Usage
-
-  $ csdx cm:bulk-publish:cross-publish --content-type [CONTENT TYPE] --source-env [SOURCE ENV] --environments [DESTINATION ENVIRONMENT] --locales [LOCALE] -a [MANAGEMENT TOKEN ALIAS] --delivery-token [DELIVERY TOKEN]
-
-
-
-  Using --config or -c flag
-
-  Generate a config file at the current working directory using `csdx cm:bulk-publish:configure -a [ALIAS]`
-
-  $ csdx cm:bulk-publish:cross-publish --config [PATH TO CONFIG FILE]
-
-  $ csdx cm:bulk-publish:cross-publish -c [PATH TO CONFIG FILE]
-
-
-
-  Using --retry-failed flag
-
-  $ csdx cm:bulk-publish:cross-publish --retry-failed [LOG FILE NAME]
-
-  $ csdx cm:bulk-publish:cross-publish -r [LOG FILE NAME]
-
-
-
-  Using --branch flag
-
-  $ csdx cm:bulk-publish:cross-publish --content-type [CONTENT TYPE] --source-env [SOURCE ENV] --environments [DESTINATION ENVIRONMENT] --locales [LOCALE] -a [MANAGEMENT TOKEN ALIAS] --delivery-token [DELIVERY TOKEN] --branch [BRANCH NAME]
-
-
-
-  Using --stack-api-key flag
-
-  $ csdx cm:bulk-publish:cross-publish --content-type [CONTENT TYPE] --source-env [SOURCE ENV] --environments [DESTINATION ENVIRONMENT] --locales [LOCALE] --stack-api-key [STACK API KEY] --delivery-token [DELIVERY TOKEN]
-
-
-
-  Using --include-variants flag
-
-  $ csdx cm:bulk-publish:cross-publish --content-type [CONTENT TYPE] --source-env [SOURCE ENV] --environments [DESTINATION ENVIRONMENT] --locales [LOCALE] --stack-api-key [STACK API KEY] --delivery-token [DELIVERY TOKEN] [--include-variants]
-```
-
-_See code: [@contentstack/cli-cm-bulk-publish](https://github.com/contentstack/cli/blob/main/packages/contentstack-bulk-publish/src/commands/cm/bulk-publish/cross-publish.js)_
-
-## `csdx cm:entries:publish [-a <value>] [--retry-failed <value>] [--bulk-publish <value>] [--publish-all-content-types] [--content-types <value>] [--locales <value>] [-e <value>] [-c <value>] [-y] [--branch <value>] [--delivery-token <value>] [--source-env <value>] [--entry-uid <value>] [--include-variants]`
-
-Publish entries from multiple contenttypes to multiple environments and locales
-
-```
-USAGE
-  $ csdx cm:bulk-publish:entries cm:entries:publish [-a <value>] [--retry-failed <value>] [--bulk-publish <value>]
-    [--publish-all-content-types] [--content-types <value>] [--locales <value>] [-e <value>] [-c <value>] [-y] [--branch
-    <value>] [--delivery-token <value>] [--source-env <value>] [--entry-uid <value>] [--include-variants]
-
-FLAGS
-  -B, --branch=<value>             [default: main] The name of the branch where you want to perform the bulk publish
-                                   operation. If you don’t mention the branch name, then by default the content from
-                                   main branch will be published.
-  -a, --alias=<value>              Alias (name) of the management token. You must use either the --alias flag or the
-                                   --stack-api-key flag.
-  -c, --config=<value>             (optional) The path of the optional configuration JSON file containing all the
-                                   options for a single run. Refer to the configure command to create a configuration
-                                   file.
-  -e, --environments=<value>...    The name of the environment on which entries will be published. In case of multiple
-                                   environments, specify their names separated by spaces.
-  -k, --stack-api-key=<value>      API key of the source stack. You must use either the --stack-api-key flag or the
-                                   --alias flag.
-  -l, --locales=<value>...         Locales in which entries will be published, e.g., en-us. In the case of multiple
-                                   locales, specify the codes separated by spaces.
-  -y, --yes                        Set it to true to process the command with the current configuration.
-      --api-version=<value>        API version to be used. Values [Default: 3, Nested Reference Publishing: 3.2].
-      --bulk-publish=<value>       [default: true] Set this flag to use Contentstack's Bulk Publish APIs. This flag is
-                                   set to true, by default.
-      --content-types=<value>...   The UID of the content type(s) whose entries you want to publish in bulk. In case of
-                                   multiple content types, specify the IDs separated by spaces.
-      --delivery-token=<value>     The delivery token of the source environment.
-      --entry-uid=<value>          Entry Uid for publish all associated variant entries.
-      --include-variants           Include Variants flag will publish all associated variant entries with base entry.
-      --publish-all-content-types  (optional) Set it to true to bulk publish entries from all content types. If the
-                                   --content-types option is already used, then you cannot use this option.
-      --retry-failed=<value>       (optional) Use this option to retry publishing the failed entries/ assets from the
-                                   logfile. Specify the name of the logfile that lists failed publish calls. If this
-                                   option is used, it will override all other flags.
-      --source-env=<value>         Source environment
-
-DESCRIPTION
-  Publish entries from multiple contenttypes to multiple environments and locales
-  The publish command is used to publish entries from the specified content types, to the
-  specified environments and locales
-
-  Note: Content Types, Environments and Locales are required to execute the command successfully
-  But, if retry-failed flag is set, then only a logfile is required
-
-
-ALIASES
-  $ csdx cm:bulk-publish:entries
-
-EXAMPLES
-  General Usage
-
-  $ csdx cm:entries:publish --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] -a [MANAGEMENT TOKEN ALIAS]
-
-
-
-  Using --config or -c flag
-
-  Generate a config file at the current working directory using `csdx cm:stacks:publish-configure -a [ALIAS]`
-
-  $ csdx cm:entries:publish --config [PATH TO CONFIG FILE]
-
-  $ csdx cm:entries:publish -c [PATH TO CONFIG FILE]
-
-
-
-  Using --retry-failed
-
-  $ csdx cm:entries:publish --retry-failed [LOG FILE NAME]
-
-  $ csdx cm:entries:publish -r [LOG FILE NAME]
-
-
-
-  Using --branch
-
-  $ csdx cm:entries:publish --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] -a [MANAGEMENT TOKEN ALIAS] --branch [BRANCH NAME]
-
-
-
-  Using --source-env
-
-  $ csdx cm:entries:publish --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] -a [MANAGEMENT TOKEN ALIAS] --source-env [SOURCE ENVIRONMENT] --delivery-token [DELIVERY TOKEN]
-
-
-
-  Using --stack-api-key
-
-  $ csdx cm:entries:publish -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] --stack-api-key [STACK API KEY] --source-env [SOURCE ENVIRONMENT] --delivery-token [DELIVERY TOKEN]
-
-
-
-  Using --include-variants
-
-  $ csdx cm:entries:publish --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] --stack-api-key [STACK API KEY] --source-env [SOURCE ENVIRONMENT] --delivery-token [DELIVERY TOKEN] [--include-variants]
-
-
-
-  Using --entry-uid and --include-variants
-
-  $ csdx cm:entries:publish --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] --stack-api-key [STACK API KEY] --source-env [SOURCE ENVIRONMENT] --delivery-token [DELIVERY TOKEN] --entry-uid [ENTRY UID] [--include-variants]
-```
-
-## `csdx cm:entries:publish-modified [-a <value>] [--retry-failed <value>] [--bulk-publish <value>] [--source-env <value>] [--content-types <value>] [--locales <value>] [-e <value>] [-c <value>] [-y] [--branch <value>]`
-
-Publish edited entries from a specified content type to the given locales and environments
-
-```
-USAGE
-  $ csdx cm:bulk-publish:entry-edits cm:entries:publish-modified [-a <value>] [--retry-failed <value>] [--bulk-publish <value>]
-    [--source-env <value>] [--content-types <value>] [--locales <value>] [-e <value>] [-c <value>] [-y] [--branch
-    <value>]
-
-FLAGS
-  -B, --branch=<value>            [default: main] The name of the branch where you want to perform the bulk publish
-                                  operation. If you don't mention the branch name, then by default the entries from main
-                                  branch will be published.
-  -a, --alias=<value>             Alias (name) of the management token. You must use either the --alias flag or the
-                                  --stack-api-key flag.
-  -c, --config=<value>            (optional) The path of the optional configuration JSON file containing all the options
-                                  for a single run. Refer to the configure command to create a configuration file.
-  -e, --environments=<value>...   The name of the environment(s) on which the entries will be published. In case of
-                                  multiple environments, specify their names separated by spaces.
-  -k, --stack-api-key=<value>     API key of the source stack. You must use either the --stack-api-key flag or the
-                                  --alias flag.
-  -l, --locales=<value>...        Locales in which entries will be published, e.g., en-us. In the case of multiple
-                                  locales, specify the codes separated by spaces.
-  -y, --yes                       Set it to true to process the command with the current configuration.
-      --api-version=<value>       API version to be used. Values [Default: 3, Nested Reference Publishing: 3.2].
-      --bulk-publish=<value>      [default: true] Set this flag to use Contentstack's Bulk Publish APIs. It is true, by
-                                  default.
-      --content-types=<value>...  The UID of the content type(s) whose edited entries you want to publish in bulk. In
-                                  case of multiple content types, specify the IDs separated by spaces.
-      --retry-failed=<value>      (optional) Use this option to retry publishing the failed entries/assets from the
-                                  logfile. Specify the name of the logfile that lists failed publish calls. If this
-                                  option is used, it will override all other flags
-      --source-env=<value>        The name of the source environment where the entries were initially published.
-
-DESCRIPTION
-  Publish edited entries from a specified content type to the given locales and environments
-  The publish-modified command is used to publish entries from the specified content types, to the
-  specified environments and locales
-
-  Note: Content type(s), Source Environment, Destination Environment(s) and Locale(s) are required to execute the
-  command successfully
-  But, if retry-failed flag is set, then only a logfile is required
-
-
-ALIASES
-  $ csdx cm:bulk-publish:entry-edits
-
-EXAMPLES
-  General Usage
-
-  $ csdx cm:entries:publish-modified --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] --source-env [SOURCE_ENV] -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] -a [MANAGEMENT TOKEN ALIAS]
-
-
-
-  Using --config or -c flag
-
-  Generate a config file at the current working directory using `csdx cm:stacks:publish-configure -a [ALIAS]`
-
-  $ csdx cm:entries:publish-modified --config [PATH TO CONFIG FILE]
-
-  $ csdx cm:entries:publish-modified -c [PATH TO CONFIG FILE]
-
-
-
-  Using --retry-failed
-
-  $ csdx cm:entries:publish-modified --retry-failed [LOG FILE NAME]
-
-  $ csdx cm:entries:publish-modified -r [LOG FILE NAME]
-
-
-
-  Using --branch
-
-  $ csdx cm:entries:publish-modified --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] --source-env [SOURCE_ENV] -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] -a [MANAGEMENT TOKEN ALIAS] --branch [BRANCH NAME]
-
-
-
-  Using --stack-api-key
-
-  $ csdx cm:entries:publish-modified --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] --source-env [SOURCE_ENV] -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] -stack-api-key [STACK API KEY]
-```
-
-## `csdx cm:entries:publish-non-localized-fields [-a <value>] [--retry-failed <value>] [--bulk-publish <value>] [--source-env <value>] [--content-types <value>] [-e <value>] [-c <value>] [-y] [--branch <value>]`
-
-Publish non-localized fields for the given content types, from a particular source environment to the specified environments
-
-```
-USAGE
-  $ csdx cm:bulk-publish:nonlocalized-field-changes cm:entries:publish-non-localized-fields [-a <value>] [--retry-failed <value>]
-    [--bulk-publish <value>] [--source-env <value>] [--content-types <value>] [-e <value>] [-c <value>] [-y] [--branch
-    <value>]
-
-FLAGS
-  -B, --branch=<value>            [default: main] The name of the branch where you want to perform the bulk publish
-                                  operation. If you don’t mention the branch name, then by default the content from the
-                                  main branch will be published.
-  -a, --alias=<value>             Alias (name) of the management token. You must use either the --alias flag or the
-                                  --stack-api-key flag.
-  -c, --config=<value>            (optional) The path of the optional configuration JSON file containing all the options
-                                  for a single run. Refer to the configure command to create a configuration file.
-  -e, --environments=<value>...   The name of the environment on which entries will be published. In case of multiple
-                                  environments, specify their names separated by spaces.
-  -k, --stack-api-key=<value>     API key of the source stack. You must use either the --stack-api-key flag or the
-                                  --alias flag.
-  -y, --yes                       Set it to true to process the command with the current configuration.
-      --api-version=<value>       API version to be used. Values [Default: 3, Nested Reference Publishing: 3.2].
-      --bulk-publish=<value>      [default: true] Set this flag to use Contentstack’s Bulk Publish APIs. It is true, by
-                                  default.
-      --content-types=<value>...  The UID of the content type whose entries you want to publish in bulk. In case of
-                                  multiple content types, specify their IDs separated by spaces.
-      --retry-failed=<value>      Use this option to retry publishing the failed entries from the logfile. Specify the
-                                  name of the logfile that lists failed publish calls. If this option is used, it will
-                                  override all other flags.
-      --source-env=<value>        The name of the source environment.
-
-DESCRIPTION
-  Publish non-localized fields for the given content types, from a particular source environment to the specified
-  environments
-  The non-localized field changes command is used to publish non-localized field changes from the given content types to
-  the specified environments
-
-  Note: Content types, Environments and Source Environment are required to execute this command successfully.
-  But, if retryFailed flag is set, then only a logfile is required
-
-ALIASES
-  $ csdx cm:bulk-publish:nonlocalized-field-changes
-
-EXAMPLES
-  General Usage
-
-  $ csdx cm:entries:publish-non-localized-fields --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] --environments [ENVIRONMENT 1] [ENVIRONMENT 2] --alias [MANAGEMENT TOKEN ALIAS] --source-env [SOURCE ENV]
-
-
-
-  Using --config or -c flag
-
-  Generate a config file at the current working directory using `csdx cm:bulk-publish:configure -a [ALIAS]`
-
-  $ csdx cm:entries:publish-non-localized-fields --config [PATH TO CONFIG FILE]
-
-  $ csdx cm:entries:publish-non-localized-fields -c [PATH TO CONFIG FILE]
-
-
-
-  Using --retry-failed flag
-
-  $ csdx cm:entries:publish-non-localized-fields --retry-failed [LOG FILE NAME]
-
-
-
-  Using --branch flag
-
-  $ csdx cm:entries:publish-non-localized-fields --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] --environments [ENVIRONMENT 1] [ENVIRONMENT 2] --alias [MANAGEMENT TOKEN ALIAS] --source-env [SOURCE ENV] --branch [BRANCH NAME]
-
-
-
-  Using --stack-api-key flag
-
-  $ csdx cm:entries:publish-non-localized-fields --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] --environments [ENVIRONMENT 1] [ENVIRONMENT 2] --stack-api-key [STACK API KEY] --source-env [SOURCE ENV]
-```
-
-## `csdx cm:bulk-publish:revert`
-
-Revert publish operations by using a log file
-
-```
-USAGE
-  $ csdx cm:bulk-publish:revert [--retry-failed <value>] [--log-file <value>]
-
-FLAGS
-  --log-file=<value>      Path of the success logfile of a particular publish action.
-  --retry-failed=<value>  (optional)  Use this option to retry publishing the failed entries from the logfile. Specify
-                          the name of the logfile that lists failed publish calls. If this option is used, it will
-                          override all other flags.
-
-DESCRIPTION
-  Revert publish operations by using a log file
-  The revert command is used to revert all publish operations performed using bulk-publish script.
-  A log file name is required to execute revert command
-
-
-ALIASES
-  $ csdx cm:bulk-publish:revert
-
-EXAMPLES
-  Using --log-file
-
-  cm:bulk-publish:revert --log-file [LOG FILE NAME]
-
-
-
-  Using --retry-failed
-
-  cm:bulk-publish:revert --retry-failed [LOG FILE NAME]
-```
-
-## `csdx csdx cm:stacks:unpublish [-a <value>] [-e <value>] [-c <value>] [-y] [--locale <value>] [--branch <value>] [--retry-failed <value>] [--bulk-unpublish <value>] [--content-type <value>] [--delivery-token <value>] [--only-assets] [--only-entries]`
-
-Unpublish entries or assets of given content types from the specified environment
-
-```
-USAGE
-  $ csdx cm:bulk-publish:unpublish csdx cm:stacks:unpublish [-a <value>] [-e <value>] [-c <value>] [-y] [--locale <value>]
-    [--branch <value>] [--retry-failed <value>] [--bulk-unpublish <value>] [--content-type <value>] [--delivery-token
-    <value>] [--only-assets] [--only-entries]
-
-FLAGS
-  -B, --branch=<value>          [default: main] Specify the branch to fetch the content from (default is main branch)
-  -a, --alias=<value>           Alias(name) for the management token
-  -c, --config=<value>          Path to the config file
-  -e, --environment=<value>     Source Environment
-  -k, --stack-api-key=<value>   Stack API key to be used
-  -l, --locale=<value>          Locale filter
-  -y, --yes                     Agree to process the command with the current configuration
-      --api-version=<value>     API version to be used. Values [Default: 3, Nested Reference Publishing: 3.2].
-      --bulk-unpublish=<value>  [default: true] This flag is set to true by default. It indicates that contentstack's
-                                bulkpublish API will be used to unpublish the entries and assets
-      --content-type=<value>    Content type filter
-      --delivery-token=<value>  The delivery token of the source environment.
-      --retry-failed=<value>    Retry publishing failed entries from the logfile (optional, overrides all other flags)
-
-DESCRIPTION
-  Unpublish entries or assets of given content types from the specified environment
-  The unpublish command is used to unpublish entries or assets from given environment
-
-  Environment (Source Environment) and Locale are required to execute the command successfully
-  But, if retry-failed flag is set, then only a logfile is required
-
-  A content type can be specified for unpublishing entries, but if no content-type(s) is/are specified and --only-assets
-  is not used,
-  then all entries from all content types will be unpublished from the source environment
-
-  Note: --only-assets can be used to unpublish only assets and --only-entries can be used to unpublish only entries.
-  (--only-assets and --only-entries cannot be used together at the same time)
-
-
-ALIASES
-  $ csdx cm:bulk-publish:unpublish
-
-EXAMPLES
-  General Usage
-
-  $ csdx cm:stacks:unpublish --bulk-unpublish --content-type [CONTENT TYPE] --environment [SOURCE ENV] --locale [LOCALE] --alias [MANAGEMENT TOKEN ALIAS] ----delivery-token [DELIVERY TOKEN]
-
-
-
-  Using --config or -c flag
-
-  Generate a config file at the current working directory using `csdx cm:bulk-publish:configure --alias [ALIAS]`
-
-  $ csdx cm:stacks:unpublish --config [PATH TO CONFIG FILE]
-
-  $ csdx cm:stacks:unpublish -c [PATH TO CONFIG FILE]
-
-
-
-  Using --retry-failed flag
-
-  $ csdx cm:stacks:unpublish --retry-failed [LOG FILE NAME]
-
-
-
-  No content type
-
-  $ csdx cm:stacks:unpublish --environment [SOURCE ENV] --locale [LOCALE] (Will unpublish all entries from all content types and assets from the source environment)
-
-
-
-  Using --only-assets
-
-  $ csdx cm:stacks:unpublish --environment [SOURCE ENV] --locale [LOCALE] --only-assets (Will unpublish only assets from the source environment)
-
-
-
-  Using --only-entries
-
-  $ csdx cm:stacks:unpublish --environment [SOURCE ENV] --locale [LOCALE] --only-entries (Will unpublish only entries, all entries, from the source environment)
-
-  $ csdx cm:stacks:unpublish --contentType [CONTENT TYPE] --environment [SOURCE ENV] --locale [LOCALE] --only-entries (Will unpublish only entries, (from CONTENT TYPE) from the source environment)
-
-
-
-  Using --branch flag
-
-  $ csdx cm:stacks:unpublish --bulk-unpublish --content-type [CONTENT TYPE] --environment [SOURCE ENV] --locale [LOCALE] --alias [MANAGEMENT TOKEN ALIAS] --delivery-token [DELIVERY TOKEN] --branch [BRANCH NAME]
-
-
-
-  Using --stack-api-key flag
-
-  $ csdx cm:stacks:unpublish --bulk-unpublish --content-type [CONTENT TYPE] --environment [SOURCE ENV] --locale [LOCALE] --stack-api-key [STACK API KEY] --delivery-token [DELIVERY TOKEN]
-```
-
-## `csdx cm:entries:publish-only-unpublished [-a <value>] [--retry-failed <value>] [--bulk-publish <value>] [--source-env <value>] [--content-types <value>] [--locales <value>] [-e <value>] [-c <value>] [-y] [--branch <value>]`
-
-Publish unpublished entries from the source environment, to other environments and locales
-
-```
-USAGE
-  $ csdx cm:bulk-publish:unpublished-entries cm:entries:publish-only-unpublished [-a <value>] [--retry-failed <value>] [--bulk-publish
-    <value>] [--source-env <value>] [--content-types <value>] [--locales <value>] [-e <value>] [-c <value>] [-y]
-    [--branch <value>]
-
-FLAGS
-  -B, --branch=<value>            [default: main] The name of the branch where you want to perform the bulk publish
-                                  operation. If you don't mention the branch name, then by default the entries from main
-                                  branch will be published.
-  -a, --alias=<value>             Alias (name) of the management token. You must use either the --alias flag or the
-                                  --stack-api-key flag.
-  -b, --bulk-publish=<value>      [default: true] Set this flag to use Contentstack's Bulk Publish APIs. It is true, by
-                                  default.
-  -c, --config=<value>            (optional)  The path of the optional configuration JSON file containing all the
-                                  options for a single run. Refer to the configure command to create a configuration
-                                  file.
-  -e, --environments=<value>...   The name of the environment on which entries will be published. In case of multiple
-                                  environments, specify their names separated by spaces.
-  -k, --stack-api-key=<value>     API key of the source stack. You must use either the --stack-api-key flag or the
-                                  --alias flag.
-  -y, --yes                       Set it to true to process the command with the current configuration.
-      --api-version=<value>       API version to be used. Values [Default: 3, Nested Reference Publishing: 3.2]..
-      --content-types=<value>...  The UID of the content type(s) whose entries you want to publish in bulk. In case of
-                                  multiple content types, specify their IDs separated by spaces.
-      --locales=<value>           Locale in which entries will be published, e.g., en-us
-      --retry-failed=<value>      (optional) Use this option to retry publishing the failed entries from the logfile. It
-                                  is optional. Specify the name of the logfile that lists failed publish calls. If this
-                                  option is used, it will override all other flags.
-      --source-env=<value>        The name of the source environment where the entries were initially published.
-
-DESCRIPTION
-  Publish unpublished entries from the source environment, to other environments and locales
-  The publish-only-unpublished command is used to publish unpublished entries from the source environment, to other
-  environments and locales
-
-  Note: Content type(s), Source Environment, Destination Environment(s) and Source Locale are required to execute the
-  command successfully
-  But, if retry-failed flag is set, then only a logfile is required
-
-
-ALIASES
-  $ csdx cm:bulk-publish:unpublished-entries
-
-EXAMPLES
-  General Usage
-
-  $ csdx cm:entries:publish-only-unpublished -b --content-types [CONTENT TYPES] -e [ENVIRONMENTS] --locales LOCALE -a [MANAGEMENT TOKEN ALIAS] -source-env [SOURCE ENV]
-
-
-
-  Using --config or -c flag
-
-  Generate a config file at the current working directory using `csdx cm:bulk-publish:configure -a [ALIAS]`
-
-  $ csdx cm:entries:publish-only-unpublished --config [PATH TO CONFIG FILE]
-
-  $ csdx cm:entries:publish-only-unpublished -c [PATH TO CONFIG FILE]
-
-
-
-  Using --retry-failed
-
-  $ csdx cm:entries:publish-only-unpublished --retry-failed [LOG FILE NAME]
-
-
-
-  Using --branch
-
-  $ csdx cm:entries:publish-only-unpublished -b --content-types [CONTENT TYPES] -e [ENVIRONMENTS] --locales LOCALE -a [MANAGEMENT TOKEN ALIAS] --branch [BRANCH NAME] -source-env [SOURCE ENV]
-
-
-
-  Using --stack-api-key
-
-  $ csdx cm:entries:publish-only-unpublished -b --content-types [CONTENT TYPES] -e [ENVIRONMENTS] --locales LOCALE -a [MANAGEMENT TOKEN ALIAS] --stack-api-key [STACK API KEY] -source-env [SOURCE ENV]
-```
-
-## `csdx cm:entries:migrate-html-rte`
-
-Migration script to migrate content from HTML RTE to JSON RTE
-
-```
-USAGE
-  $ csdx cm:entries:migrate-html-rte [-c <value>] [-a <value>] [--stack-api-key <value>] [--content-type <value>]
-    [--global-field] [-y] [--branch <value>] [--html-path <value> --json-path <value>] [--delay <value>] [--locale
-    <value>] [--batch-limit <value>]
-
-FLAGS
-  -a, --alias=<value>          Enter the alias name. You must use either the --alias flag or the --stack-api-key flag.
-  -c, --config-path=<value>    Specify the path where your config file is located.
-  -y, --yes                    Avoids reconfirmation of your configuration.
-      --batch-limit=<value>    [default: 50] Provide batch limit for updating entries (default: 50).
-      --branch=<value>         The name of the branch to be used.
-      --content-type=<value>   Specify the UID of the content type for which you want to migrate HTML RTE content.
-      --delay=<value>          [default: 1000] To set the interval time between the migration of HTML RTE to JSON RTE in
-                               subsequent entries of a content type. The default value is 1,000 milliseconds.
-      --global-field           Checks whether the specified UID belongs to a content type or a global field. This flag
-                               is set to false by default.
-      --html-path=<value>      Enter the path to the HTML RTE whose content you want to migrate.
-      --json-path=<value>      Enter the path to the JSON RTE to which you want to migrate the HTML RTE content.
-      --locale=<value>         The locale from which entries will be migrated.
-      --stack-api-key=<value>  API key of the source stack. You must use either the --stack-api-key flag or the --alias
-                               flag.
-
-DESCRIPTION
-  Migration script to migrate content from HTML RTE to JSON RTE
-
-EXAMPLES
-  General Usage
-
-  $ csdx cm:entries:migrate-html-rte --config-path path/to/config.json
-
-
-
-  Using Flags
-
-  $ csdx cm:entries:migrate-html-rte --alias alias --content-type content_type_uid --html-path html-path --json-path json-path
-
-
-
-  Nested RTE
-
-  $ csdx cm:entries:migrate-html-rte --alias alias --content-type content_type_uid --html-path modular_block_uid.block_uid.html_rte_uid --json-path modular_block_uid.block_uid.json_rte_uid
-
-
-
-  $ csdx cm:entries:migrate-html-rte --alias alias --content-type content_type_uid --html-path group_uid.html_rte_uid --json-path group_uid.json_rte_uid
-
-
-
-  Global Field
-
-  $ csdx cm:entries:migrate-html-rte --alias alias --content-type global_field_uid --global-field --html-path html-path --json-path json-path
-```
-
-_See code: [@contentstack/cli-cm-migrate-rte](https://github.com/contentstack/cli-plugins/blob/main/packages/contentstack-migrate-rte/src/commands/cm/entries/migrate-html-rte.js)_
-
-## `csdx cm:entries:publish [-a <value>] [--retry-failed <value>] [--bulk-publish <value>] [--publish-all-content-types] [--content-types <value>] [--locales <value>] [-e <value>] [-c <value>] [-y] [--branch <value>] [--delivery-token <value>] [--source-env <value>] [--entry-uid <value>] [--include-variants]`
-
-Publish entries from multiple contenttypes to multiple environments and locales
-
-```
-USAGE
-  $ csdx cm:entries:publish [-a <value>] [--retry-failed <value>] [--bulk-publish <value>] [--publish-all-content-types]
-    [--content-types <value>] [--locales <value>] [-e <value>] [-c <value>] [-y] [--branch <value>] [--delivery-token
-    <value>] [--source-env <value>] [--entry-uid <value>] [--include-variants]
-
-FLAGS
-  -B, --branch=<value>             [default: main] The name of the branch where you want to perform the bulk publish
-                                   operation. If you don’t mention the branch name, then by default the content from
-                                   main branch will be published.
-  -a, --alias=<value>              Alias (name) of the management token. You must use either the --alias flag or the
-                                   --stack-api-key flag.
-  -c, --config=<value>             (optional) The path of the optional configuration JSON file containing all the
-                                   options for a single run. Refer to the configure command to create a configuration
-                                   file.
-  -e, --environments=<value>...    The name of the environment on which entries will be published. In case of multiple
-                                   environments, specify their names separated by spaces.
-  -k, --stack-api-key=<value>      API key of the source stack. You must use either the --stack-api-key flag or the
-                                   --alias flag.
-  -l, --locales=<value>...         Locales in which entries will be published, e.g., en-us. In the case of multiple
-                                   locales, specify the codes separated by spaces.
-  -y, --yes                        Set it to true to process the command with the current configuration.
-      --api-version=<value>        API version to be used. Values [Default: 3, Nested Reference Publishing: 3.2].
-      --bulk-publish=<value>       [default: true] Set this flag to use Contentstack's Bulk Publish APIs. This flag is
-                                   set to true, by default.
-      --content-types=<value>...   The UID of the content type(s) whose entries you want to publish in bulk. In case of
-                                   multiple content types, specify the IDs separated by spaces.
-      --delivery-token=<value>     The delivery token of the source environment.
-      --entry-uid=<value>          Entry Uid for publish all associated variant entries.
-      --include-variants           Include Variants flag will publish all associated variant entries with base entry.
-      --publish-all-content-types  (optional) Set it to true to bulk publish entries from all content types. If the
-                                   --content-types option is already used, then you cannot use this option.
-      --retry-failed=<value>       (optional) Use this option to retry publishing the failed entries/ assets from the
-                                   logfile. Specify the name of the logfile that lists failed publish calls. If this
-                                   option is used, it will override all other flags.
-      --source-env=<value>         Source environment
-
-DESCRIPTION
-  Publish entries from multiple contenttypes to multiple environments and locales
-  The publish command is used to publish entries from the specified content types, to the
-  specified environments and locales
-
-  Note: Content Types, Environments and Locales are required to execute the command successfully
-  But, if retry-failed flag is set, then only a logfile is required
-
-
-ALIASES
-  $ csdx cm:bulk-publish:entries
-
-EXAMPLES
-  General Usage
-
-  $ csdx cm:entries:publish --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] -a [MANAGEMENT TOKEN ALIAS]
-
-
-
-  Using --config or -c flag
-
-  Generate a config file at the current working directory using `csdx cm:stacks:publish-configure -a [ALIAS]`
-
-  $ csdx cm:entries:publish --config [PATH TO CONFIG FILE]
-
-  $ csdx cm:entries:publish -c [PATH TO CONFIG FILE]
-
-
-
-  Using --retry-failed
-
-  $ csdx cm:entries:publish --retry-failed [LOG FILE NAME]
-
-  $ csdx cm:entries:publish -r [LOG FILE NAME]
-
-
-
-  Using --branch
-
-  $ csdx cm:entries:publish --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] -a [MANAGEMENT TOKEN ALIAS] --branch [BRANCH NAME]
-
-
-
-  Using --source-env
-
-  $ csdx cm:entries:publish --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] -a [MANAGEMENT TOKEN ALIAS] --source-env [SOURCE ENVIRONMENT] --delivery-token [DELIVERY TOKEN]
-
-
-
-  Using --stack-api-key
-
-  $ csdx cm:entries:publish -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] --stack-api-key [STACK API KEY] --source-env [SOURCE ENVIRONMENT] --delivery-token [DELIVERY TOKEN]
-
-
-
-  Using --include-variants
-
-  $ csdx cm:entries:publish --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] --stack-api-key [STACK API KEY] --source-env [SOURCE ENVIRONMENT] --delivery-token [DELIVERY TOKEN] [--include-variants]
-
-
-
-  Using --entry-uid and --include-variants
-
-  $ csdx cm:entries:publish --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] --stack-api-key [STACK API KEY] --source-env [SOURCE ENVIRONMENT] --delivery-token [DELIVERY TOKEN] --entry-uid [ENTRY UID] [--include-variants]
-```
-
-_See code: [@contentstack/cli-cm-bulk-publish](https://github.com/contentstack/cli/blob/main/packages/contentstack-bulk-publish/src/commands/cm/entries/publish.js)_
-
-## `csdx cm:entries:publish-modified [-a <value>] [--retry-failed <value>] [--bulk-publish <value>] [--source-env <value>] [--content-types <value>] [--locales <value>] [-e <value>] [-c <value>] [-y] [--branch <value>]`
-
-Publish edited entries from a specified content type to the given locales and environments
-
-```
-USAGE
-  $ csdx cm:entries:publish-modified [-a <value>] [--retry-failed <value>] [--bulk-publish <value>] [--source-env <value>]
-    [--content-types <value>] [--locales <value>] [-e <value>] [-c <value>] [-y] [--branch <value>]
-
-FLAGS
-  -B, --branch=<value>            [default: main] The name of the branch where you want to perform the bulk publish
-                                  operation. If you don't mention the branch name, then by default the entries from main
-                                  branch will be published.
-  -a, --alias=<value>             Alias (name) of the management token. You must use either the --alias flag or the
-                                  --stack-api-key flag.
-  -c, --config=<value>            (optional) The path of the optional configuration JSON file containing all the options
-                                  for a single run. Refer to the configure command to create a configuration file.
-  -e, --environments=<value>...   The name of the environment(s) on which the entries will be published. In case of
-                                  multiple environments, specify their names separated by spaces.
-  -k, --stack-api-key=<value>     API key of the source stack. You must use either the --stack-api-key flag or the
-                                  --alias flag.
-  -l, --locales=<value>...        Locales in which entries will be published, e.g., en-us. In the case of multiple
-                                  locales, specify the codes separated by spaces.
-  -y, --yes                       Set it to true to process the command with the current configuration.
-      --api-version=<value>       API version to be used. Values [Default: 3, Nested Reference Publishing: 3.2].
-      --bulk-publish=<value>      [default: true] Set this flag to use Contentstack's Bulk Publish APIs. It is true, by
-                                  default.
-      --content-types=<value>...  The UID of the content type(s) whose edited entries you want to publish in bulk. In
-                                  case of multiple content types, specify the IDs separated by spaces.
-      --retry-failed=<value>      (optional) Use this option to retry publishing the failed entries/assets from the
-                                  logfile. Specify the name of the logfile that lists failed publish calls. If this
-                                  option is used, it will override all other flags
-      --source-env=<value>        The name of the source environment where the entries were initially published.
-
-DESCRIPTION
-  Publish edited entries from a specified content type to the given locales and environments
-  The publish-modified command is used to publish entries from the specified content types, to the
-  specified environments and locales
-
-  Note: Content type(s), Source Environment, Destination Environment(s) and Locale(s) are required to execute the
-  command successfully
-  But, if retry-failed flag is set, then only a logfile is required
-
-
-ALIASES
-  $ csdx cm:bulk-publish:entry-edits
-
-EXAMPLES
-  General Usage
-
-  $ csdx cm:entries:publish-modified --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] --source-env [SOURCE_ENV] -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] -a [MANAGEMENT TOKEN ALIAS]
-
-
-
-  Using --config or -c flag
-
-  Generate a config file at the current working directory using `csdx cm:stacks:publish-configure -a [ALIAS]`
-
-  $ csdx cm:entries:publish-modified --config [PATH TO CONFIG FILE]
-
-  $ csdx cm:entries:publish-modified -c [PATH TO CONFIG FILE]
-
-
-
-  Using --retry-failed
-
-  $ csdx cm:entries:publish-modified --retry-failed [LOG FILE NAME]
-
-  $ csdx cm:entries:publish-modified -r [LOG FILE NAME]
-
-
-
-  Using --branch
-
-  $ csdx cm:entries:publish-modified --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] --source-env [SOURCE_ENV] -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] -a [MANAGEMENT TOKEN ALIAS] --branch [BRANCH NAME]
-
-
-
-  Using --stack-api-key
-
-  $ csdx cm:entries:publish-modified --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] --source-env [SOURCE_ENV] -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] -stack-api-key [STACK API KEY]
-```
-
-_See code: [@contentstack/cli-cm-bulk-publish](https://github.com/contentstack/cli/blob/main/packages/contentstack-bulk-publish/src/commands/cm/entries/publish-modified.js)_
-
-## `csdx cm:entries:publish-non-localized-fields [-a <value>] [--retry-failed <value>] [--bulk-publish <value>] [--source-env <value>] [--content-types <value>] [-e <value>] [-c <value>] [-y] [--branch <value>]`
-
-Publish non-localized fields for the given content types, from a particular source environment to the specified environments
-
-```
-USAGE
-  $ csdx cm:entries:publish-non-localized-fields [-a <value>] [--retry-failed <value>] [--bulk-publish <value>] [--source-env <value>]
-    [--content-types <value>] [-e <value>] [-c <value>] [-y] [--branch <value>]
-
-FLAGS
-  -B, --branch=<value>            [default: main] The name of the branch where you want to perform the bulk publish
-                                  operation. If you don’t mention the branch name, then by default the content from the
-                                  main branch will be published.
-  -a, --alias=<value>             Alias (name) of the management token. You must use either the --alias flag or the
-                                  --stack-api-key flag.
-  -c, --config=<value>            (optional) The path of the optional configuration JSON file containing all the options
-                                  for a single run. Refer to the configure command to create a configuration file.
-  -e, --environments=<value>...   The name of the environment on which entries will be published. In case of multiple
-                                  environments, specify their names separated by spaces.
-  -k, --stack-api-key=<value>     API key of the source stack. You must use either the --stack-api-key flag or the
-                                  --alias flag.
-  -y, --yes                       Set it to true to process the command with the current configuration.
-      --api-version=<value>       API version to be used. Values [Default: 3, Nested Reference Publishing: 3.2].
-      --bulk-publish=<value>      [default: true] Set this flag to use Contentstack’s Bulk Publish APIs. It is true, by
-                                  default.
-      --content-types=<value>...  The UID of the content type whose entries you want to publish in bulk. In case of
-                                  multiple content types, specify their IDs separated by spaces.
-      --retry-failed=<value>      Use this option to retry publishing the failed entries from the logfile. Specify the
-                                  name of the logfile that lists failed publish calls. If this option is used, it will
-                                  override all other flags.
-      --source-env=<value>        The name of the source environment.
-
-DESCRIPTION
-  Publish non-localized fields for the given content types, from a particular source environment to the specified
-  environments
-  The non-localized field changes command is used to publish non-localized field changes from the given content types to
-  the specified environments
-
-  Note: Content types, Environments and Source Environment are required to execute this command successfully.
-  But, if retryFailed flag is set, then only a logfile is required
-
-ALIASES
-  $ csdx cm:bulk-publish:nonlocalized-field-changes
-
-EXAMPLES
-  General Usage
-
-  $ csdx cm:entries:publish-non-localized-fields --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] --environments [ENVIRONMENT 1] [ENVIRONMENT 2] --alias [MANAGEMENT TOKEN ALIAS] --source-env [SOURCE ENV]
-
-
-
-  Using --config or -c flag
-
-  Generate a config file at the current working directory using `csdx cm:bulk-publish:configure -a [ALIAS]`
-
-  $ csdx cm:entries:publish-non-localized-fields --config [PATH TO CONFIG FILE]
-
-  $ csdx cm:entries:publish-non-localized-fields -c [PATH TO CONFIG FILE]
-
-
-
-  Using --retry-failed flag
-
-  $ csdx cm:entries:publish-non-localized-fields --retry-failed [LOG FILE NAME]
-
-
-
-  Using --branch flag
-
-  $ csdx cm:entries:publish-non-localized-fields --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] --environments [ENVIRONMENT 1] [ENVIRONMENT 2] --alias [MANAGEMENT TOKEN ALIAS] --source-env [SOURCE ENV] --branch [BRANCH NAME]
-
-
-
-  Using --stack-api-key flag
-
-  $ csdx cm:entries:publish-non-localized-fields --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] --environments [ENVIRONMENT 1] [ENVIRONMENT 2] --stack-api-key [STACK API KEY] --source-env [SOURCE ENV]
-```
-
-_See code: [@contentstack/cli-cm-bulk-publish](https://github.com/contentstack/cli/blob/main/packages/contentstack-bulk-publish/src/commands/cm/entries/publish-non-localized-fields.js)_
-
-## `csdx cm:entries:publish-only-unpublished [-a <value>] [--retry-failed <value>] [--bulk-publish <value>] [--source-env <value>] [--content-types <value>] [--locales <value>] [-e <value>] [-c <value>] [-y] [--branch <value>]`
-
-Publish unpublished entries from the source environment, to other environments and locales
-
-```
-USAGE
-  $ csdx cm:entries:publish-only-unpublished [-a <value>] [--retry-failed <value>] [--bulk-publish <value>] [--source-env <value>]
-    [--content-types <value>] [--locales <value>] [-e <value>] [-c <value>] [-y] [--branch <value>]
-
-FLAGS
-  -B, --branch=<value>            [default: main] The name of the branch where you want to perform the bulk publish
-                                  operation. If you don't mention the branch name, then by default the entries from main
-                                  branch will be published.
-  -a, --alias=<value>             Alias (name) of the management token. You must use either the --alias flag or the
-                                  --stack-api-key flag.
-  -b, --bulk-publish=<value>      [default: true] Set this flag to use Contentstack's Bulk Publish APIs. It is true, by
-                                  default.
-  -c, --config=<value>            (optional)  The path of the optional configuration JSON file containing all the
-                                  options for a single run. Refer to the configure command to create a configuration
-                                  file.
-  -e, --environments=<value>...   The name of the environment on which entries will be published. In case of multiple
-                                  environments, specify their names separated by spaces.
-  -k, --stack-api-key=<value>     API key of the source stack. You must use either the --stack-api-key flag or the
-                                  --alias flag.
-  -y, --yes                       Set it to true to process the command with the current configuration.
-      --api-version=<value>       API version to be used. Values [Default: 3, Nested Reference Publishing: 3.2]..
-      --content-types=<value>...  The UID of the content type(s) whose entries you want to publish in bulk. In case of
-                                  multiple content types, specify their IDs separated by spaces.
-      --locales=<value>           Locale in which entries will be published, e.g., en-us
-      --retry-failed=<value>      (optional) Use this option to retry publishing the failed entries from the logfile. It
-                                  is optional. Specify the name of the logfile that lists failed publish calls. If this
-                                  option is used, it will override all other flags.
-      --source-env=<value>        The name of the source environment where the entries were initially published.
-
-DESCRIPTION
-  Publish unpublished entries from the source environment, to other environments and locales
-  The publish-only-unpublished command is used to publish unpublished entries from the source environment, to other
-  environments and locales
-
-  Note: Content type(s), Source Environment, Destination Environment(s) and Source Locale are required to execute the
-  command successfully
-  But, if retry-failed flag is set, then only a logfile is required
-
-
-ALIASES
-  $ csdx cm:bulk-publish:unpublished-entries
-
-EXAMPLES
-  General Usage
-
-  $ csdx cm:entries:publish-only-unpublished -b --content-types [CONTENT TYPES] -e [ENVIRONMENTS] --locales LOCALE -a [MANAGEMENT TOKEN ALIAS] -source-env [SOURCE ENV]
-
-
-
-  Using --config or -c flag
-
-  Generate a config file at the current working directory using `csdx cm:bulk-publish:configure -a [ALIAS]`
-
-  $ csdx cm:entries:publish-only-unpublished --config [PATH TO CONFIG FILE]
-
-  $ csdx cm:entries:publish-only-unpublished -c [PATH TO CONFIG FILE]
-
-
-
-  Using --retry-failed
-
-  $ csdx cm:entries:publish-only-unpublished --retry-failed [LOG FILE NAME]
-
-
-
-  Using --branch
-
-  $ csdx cm:entries:publish-only-unpublished -b --content-types [CONTENT TYPES] -e [ENVIRONMENTS] --locales LOCALE -a [MANAGEMENT TOKEN ALIAS] --branch [BRANCH NAME] -source-env [SOURCE ENV]
-
-
-
-  Using --stack-api-key
-
-  $ csdx cm:entries:publish-only-unpublished -b --content-types [CONTENT TYPES] -e [ENVIRONMENTS] --locales LOCALE -a [MANAGEMENT TOKEN ALIAS] --stack-api-key [STACK API KEY] -source-env [SOURCE ENV]
-```
-
-_See code: [@contentstack/cli-cm-bulk-publish](https://github.com/contentstack/cli/blob/main/packages/contentstack-bulk-publish/src/commands/cm/entries/publish-only-unpublished.js)_
-
-## `csdx cm:entries:unpublish`
-
-Unpublish entries from the given environment
-
-```
-USAGE
-  $ csdx cm:entries:unpublish [-a <value>] [-k <value>] [-e <value>] [-c <value>] [-y] [--locale <value>] [--branch
-    <value>] [--retry-failed <value>] [--bulk-unpublish <value>] [--api-version <value>] [--content-type <value>]
-    [--delivery-token <value>] [--include-variants]
-
-FLAGS
-  -a, --alias=<value>           Alias (name) for the management token. You must use either the --alias flag or the
-                                --stack-api-key flag.
-  -c, --config=<value>          (optional) Path to the configuration JSON file containing all options for a single run.
-                                Refer to the configure command to create a configuration file.
-  -e, --environment=<value>     The name of the environment from where entries/assets need to be unpublished.
-  -k, --stack-api-key=<value>   API key of the source stack. You must use either the --stack-api-key flag or the --alias
-                                flag.
-  -y, --yes                     Set to true to process the command with the current configuration.
-      --api-version=<value>     API version to be used. Values [Default: 3, Nested Reference Publishing: 3.2].
-      --branch=<value>          [default: main] Specify the branch to fetch the content. If not mentioned, the main
-                                branch will be used by default.
-      --bulk-unpublish=<value>  [default: true] This flag is set to true by default. It indicates that Contentstack's
-                                Bulk Publish APIs will be used to unpublish the entries.
-      --content-type=<value>    The UID of the content type whose entries you want to unpublish in bulk.
-      --delivery-token=<value>  The delivery token of the source environment.
-      --include-variants        Include Variants flag will unpublish all associated variant entries.
-      --locale=<value>          Locale from which entries/assets will be unpublished, e.g., en-us.
-      --retry-failed=<value>    (optional) Use this option to retry unpublishing the failed entries from the logfile.
-                                Specify the name of the logfile that lists failed unpublish calls. If used, this option
-                                will override all other flags.
-
-DESCRIPTION
-  Unpublish entries from the given environment
-  The unpublish command is used to unpublish entries from the given environment
-
-  Note: Environment (Source Environment) and Locale are required to execute the command successfully
-  But, if retry-failed flag is set, then only a logfile is required
-
-EXAMPLES
-  General Usage
-
-  $ csdx cm:stacks:unpublish --bulk-unpublish --content-type [CONTENT TYPE] --environment [SOURCE ENV] --locale [LOCALE] --alias [MANAGEMENT TOKEN ALIAS] --delivery-token [DELIVERY TOKEN]
-
-
-
-  Using --config or -c flag
-
-  Generate a config file at the current working directory using `csdx cm:bulk-publish:configure --alias [ALIAS]`
-
-  $ csdx cm:stacks:unpublish --config [PATH TO CONFIG FILE]
-
-  $ csdx cm:stacks:unpublish -c [PATH TO CONFIG FILE]
-
-
-
-  Using --retry-failed flag
-
-  $ csdx cm:stacks:unpublish --retry-failed [LOG FILE NAME]
-
-
-
-  Using --branch flag
-
-  $ csdx cm:stacks:unpublish --bulk-unpublish --content-type [CONTENT TYPE] --environment [SOURCE ENV] --locale [LOCALE] --alias [MANAGEMENT TOKEN ALIAS] --delivery-token [DELIVERY TOKEN] --branch [BRANCH NAME]
-
-
-
-  Using --stack-api-key flag
-
-  $ csdx cm:stacks:unpublish --bulk-unpublish --content-type [CONTENT TYPE] --environment [SOURCE ENV] --locale [LOCALE] --stack-api-key [STACK API KEY] --delivery-token [DELIVERY TOKEN]
-
-
-
-  Using --include-variants flag
-
-  $ csdx cm:stacks:unpublish --bulk-unpublish --content-type [CONTENT TYPE] --environment [SOURCE ENV] --locale [LOCALE] --stack-api-key [STACK API KEY] --delivery-token [DELIVERY TOKEN] --include-variants
-```
-
-_See code: [@contentstack/cli-cm-bulk-publish](https://github.com/contentstack/cli/blob/main/packages/contentstack-bulk-publish/src/commands/cm/entries/unpublish.js)_
-
-## `csdx cm:entries:update-and-publish [-a <value>] [--retry-failed <value>] [--bulk-publish <value>] [--content-types <value>] [-t <value>] [-e <value>] [-c <value>] [-y] [--locales <value>] [--branch <value>]`
-
-Add fields from updated content types to their respective entries
-
-```
-USAGE
-  $ csdx cm:entries:update-and-publish [-a <value>] [--retry-failed <value>] [--bulk-publish <value>] [--content-types <value>] [-t
-    <value>] [-e <value>] [-c <value>] [-y] [--locales <value>] [--branch <value>]
-
-FLAGS
-  -B, --branch=<value>            [default: main] The name of the branch where you want to perform the bulk publish
-                                  operation. If you don’t mention the branch name, then by default the content from the
-                                  main branch will be published.
-  -a, --alias=<value>             Alias (name) of the management token. You must use either the --alias flag or the
-                                  --stack-api-key flag.
-  -c, --config=<value>            (optional) The path of the optional configuration JSON file containing all the options
-                                  for a single run. Refer to the configure command to create a configuration file.
-  -e, --environments=<value>...   The name of the environment on which entries will be published. In case of multiple
-                                  environments, specify their names separated by spaces.
-  -k, --stack-api-key=<value>     API key of the source stack. You must use either the --stack-api-key flag or the
-                                  --alias flag.
-  -l, --locales=<value>...        Locales in which entries will be published, e.g., en-us. In the case of multiple
-                                  locales, specify the codes separated by spaces.
-  -t, --contentTypes=<value>...   The Contenttypes from which entries will be published.
-  -y, --yes                       Set it to true to process the command with the current configuration.
-      --api-version=<value>       API version to be used. Values [Default: 3, Nested Reference Publishing: 3.2].
-      --bulk-publish=<value>      [default: true] Set this flag to use Contentstack’s Bulk Publish APIs. It is true, by
-                                  default.
-      --content-types=<value>...  The UID of the content type ID whose entries you want to publish in bulk. In case of
-                                  multiple content types, specify their IDs separated by spaces.
-      --force                     Update and publish all entries even if no fields have been added.
-      --retry-failed=<value>      Use this option to retry publishing the failed entries from the logfile. Specify the
-                                  name of the logfile that lists failed publish calls. If this option is used, it will
-                                  override all other flags.
-
-DESCRIPTION
-  Add fields from updated content types to their respective entries
-  The update-and-publish command is used to update existing entries with the updated schema of the respective content
-  type
-
-  Note: Content types, Environments and Locales are required to execute the command successfully
-  But, if retry-failed flag is set, then only a logfile is required
-
-
-ALIASES
-  $ csdx cm:bulk-publish:add-fields
-
-EXAMPLES
-  General Usage
-
-  $ csdx cm:entries:update-and-publish --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] -a [MANAGEMENT TOKEN ALIAS]
-
-
-
-  Using --config or -c flag
-
-  Generate a config file at the current working directory using `csdx cm:stacks:publish-configure -a [ALIAS]`
-
-  $ csdx cm:entries:update-and-publish --config [PATH TO CONFIG FILE]
-
-  $ csdx cm:entries:update-and-publish -c [PATH TO CONFIG FILE]
-
-
-
-  Using --retry-failed
-
-  $ csdx cm:entries:update-and-publish --retry-failed [LOG FILE NAME]
-
-
-
-  Using --branch
-
-  $ csdx cm:entries:update-and-publish --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] -a [MANAGEMENT TOKEN ALIAS] --branch [BRANCH NAME]
-
-
-
-  Using --stack-api-key
-
-  $ csdx cm:entries:update-and-publish --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] --stack-api-key [STACK API KEY]
-```
-
-_See code: [@contentstack/cli-cm-bulk-publish](https://github.com/contentstack/cli/blob/main/packages/contentstack-bulk-publish/src/commands/cm/entries/update-and-publish.js)_
-
-## `csdx cm:stacks:export [-c <value>] [-k <value>] [-d <value>] [-a <value>] [--module <value>] [--content-types <value>] [--branch <value>] [--secured-assets]`
-
-Export content from a stack
-
-```
-USAGE
-  $ csdx cm:export cm:stacks:export [-c <value>] [-k <value>] [-d <value>] [-a <value>] [--module <value>]
-    [--content-types <value>] [--branch <value>] [--secured-assets]
-
-FLAGS
-  -B, --branch=<value>            [optional] The name of the branch where you want to export your content. If you don't
-                                  mention the branch name, then by default the content will be exported from all the
-                                  branches of your stack.
-  -a, --alias=<value>             The management token alias of the source stack from which you will export content.
-  -c, --config=<value>            [optional] Path of the config
-  -d, --data-dir=<value>          The path or the location in your file system to store the exported content. For e.g.,
-                                  ./content
-  -k, --stack-api-key=<value>     API Key of the source stack
-  -m, --module=<value>            [optional] Specific module name. If not specified, the export command will export all
-                                  the modules to the stack. The available modules are assets, content-types, entries,
-                                  environments, extensions, marketplace-apps, global-fields, labels, locales, webhooks,
-                                  workflows, custom-roles, taxonomies, and studio.
-  -t, --content-types=<value>...  [optional]  The UID of the content type(s) whose content you want to export. In case
-                                  of multiple content types, specify the IDs separated by spaces.
-  -y, --yes                       [optional] Force override all Marketplace prompts.
-      --branch-alias=<value>      (Optional) The alias of the branch from which you want to export content.
-      --secured-assets            [optional] Use this flag for assets that are secured.
-
-DESCRIPTION
-  Export content from a stack
-
-ALIASES
-  $ csdx cm:export
-
-EXAMPLES
-  $ csdx cm:stacks:export --stack-api-key <stack_api_key> --data-dir <path/of/export/destination/dir>
-
-  $ csdx cm:stacks:export --config <path/to/config/dir>
-
-  $ csdx cm:stacks:export --alias <management_token_alias>
-
-  $ csdx cm:stacks:export --alias <management_token_alias> --data-dir <path/to/export/destination/dir>
-
-  $ csdx cm:stacks:export --alias <management_token_alias> --config <path/to/config/file>
-
-  $ csdx cm:stacks:export --module <single module name>
-
-  $ csdx cm:stacks:export --branch [optional] branch name
-```
-
-## `csdx cm:export-to-csv`
-
-Export entries, taxonomies, terms or organization users to csv using this command
-
-```
-USAGE
-  $ csdx cm:export-to-csv [--action entries|users|teams|taxonomies] [-a <value>] [--org <value>] [-n <value>] [-k
-    <value>] [--org-name <value>] [--locale <value>] [--content-type <value>] [--branch <value>] [--team-uid <value>]
-    [--taxonomy-uid <value>] [--include-fallback] [--fallback-locale <value>] [--delimiter <value>]
-
-FLAGS
-  -a, --alias=<value>            Alias of the management token.
-  -k, --stack-api-key=<value>    API Key of the source stack.
-  -n, --stack-name=<value>       Name of the stack that needs to be created as CSV filename.
-      --action=<option>          Option to export data (entries, users, teams, taxonomies). <options:
-                                 entries|users|teams|taxonomies>
-                                 <options: entries|users|teams|taxonomies>
-      --branch=<value>           Branch from which entries will be exported.
-      --content-type=<value>     Content type of entries that will be exported.
-      --delimiter=<value>        [default: ,] [optional] Provide a delimiter to separate individual data fields within
-                                 the CSV file. For example: cm:export-to-csv --delimiter '|'
-      --fallback-locale=<value>  [Optional] Specify a specific fallback locale for taxonomy export. This locale will be
-                                 used when a taxonomy term doesn't exist in the primary locale. Takes priority over
-                                 branch fallback hierarchy when both are specified.
-      --include-fallback         [Optional] Include fallback locale data when exporting taxonomies. When enabled, if a
-                                 taxonomy term doesn't exist in the specified locale, it will fallback to the hierarchy
-                                 defined in the branch settings.
-      --locale=<value>           Locale of entries that will be exported.
-      --org=<value>              Provide organization UID to clone org users.
-      --org-name=<value>         Name of the organization that needs to be created as CSV filename.
-      --taxonomy-uid=<value>     Provide the taxonomy UID of the related terms you want to export.
-      --team-uid=<value>         Provide the UID of a specific team in an organization.
-
-DESCRIPTION
-  Export entries, taxonomies, terms or organization users to csv using this command
-
-ALIASES
-  $ csdx cm:export-to-csv
-
-EXAMPLES
-  $ csdx cm:export-to-csv
-
-
-
-  Exporting entries to CSV
-
-  $ csdx cm:export-to-csv --action entries --locale <locale> --alias <management-token-alias> --content-type <content-type>
-
-
-
-  Exporting entries to CSV with stack name and branch
-
-  $ csdx cm:export-to-csv --action entries --locale <locale> --alias <management-token-alias> --content-type <content-type> --stack-name <stack-name> --branch <branch-name>
-
-
-
-  Exporting organization users to CSV
-
-  $ csdx cm:export-to-csv --action users --org <org-uid>
-
-
-
-  Exporting organization teams to CSV
-
-  $ csdx cm:export-to-csv --action teams --org <org-uid>
-
-
-
-  Exporting teams with specific team UID
-
-  $ csdx cm:export-to-csv --action teams --org <org-uid> --team-uid <team-uid>
-
-
-
-  Exporting taxonomies to CSV
-
-  $ csdx cm:export-to-csv --action taxonomies --alias <management-token-alias>
-
-
-
-  Exporting specific taxonomy with locale
-
-  $ csdx cm:export-to-csv --action taxonomies --alias <management-token-alias> --taxonomy-uid <taxonomy-uid> --locale <locale>
-
-
-
-  Exporting taxonomies with fallback locale
-
-  $ csdx cm:export-to-csv --action taxonomies --alias <management-token-alias> --locale <locale> --include-fallback --fallback-locale <fallback-locale>
-```
-
-_See code: [@contentstack/cli-cm-export-to-csv](https://github.com/contentstack/cli/blob/main/packages/contentstack-export-to-csv/src/commands/cm/export-to-csv.ts)_
-
-## `csdx cm:stacks:import [-c <value>] [-k <value>] [-d <value>] [-a <value>] [--module <value>] [--backup-dir <value>] [--branch <value>] [--import-webhook-status disable|current]`
-
-Import content from a stack
-
-```
-USAGE
-  $ csdx cm:import cm:stacks:import [-c <value>] [-k <value>] [-d <value>] [-a <value>] [--module <value>]
-    [--backup-dir <value>] [--branch <value>] [--import-webhook-status disable|current]
-
-FLAGS
-  -B, --branch=<value>
-      The name of the branch where you want to import your content. If you don't mention the branch name, then by default
-      the content will be imported to the main branch.
-
-  -a, --alias=<value>
-      The management token of the destination stack where you will import the content.
-
-  -b, --backup-dir=<value>
-      [optional] Backup directory name when using specific module.
-
-  -c, --config=<value>
-      [optional] The path of the configuration JSON file containing all the options for a single run.
-
-  -d, --data-dir=<value>
-      The path or the location in your file system where the content, you intend to import, is stored. For example, -d
-      "C:\Users\Name\Desktop\cli\content". If the export folder has branches involved, then the path should point till the
-      particular branch. For example, “-d "C:\Users\Name\Desktop\cli\content\branch_name"
-
-  -k, --stack-api-key=<value>
-      API Key of the target stack
-
-  -m, --module=<value>
-      [optional] Specify the module to import into the target stack. If not specified, the import command will import all
-      the modules into the stack. The available modules are assets, content-types, entries, environments, extensions,
-      marketplace-apps, global-fields, labels, locales, webhooks, workflows, custom-roles, personalize projects,
-      taxonomies, and composable-studio.
-
-  -y, --yes
-      [optional] Force override all Marketplace prompts.
-
-  --branch-alias=<value>
-      Specify the branch alias where you want to import your content. If not specified, the content is imported into the
-      main branch by default.
-
-  --exclude-global-modules
-      Excludes the branch-independent module from the import operation.
-
-  --import-webhook-status=<option>
-      [default: disable] [default: disable] (optional) This webhook state keeps the same state of webhooks as the source
-      stack. <options: disable|current>
-      <options: disable|current>
-
-  --personalize-project-name=<value>
-      (optional) Provide a unique name for the Personalize project.
-
-  --replace-existing
-      Replaces the existing module in the target stack.
-
-  --skip-app-recreation
-      (optional) Skips the recreation of private apps if they already exist.
-
-  --skip-assets-publish
-      Skips asset publishing during the import process.
-
-  --skip-audit
-      Skips the audit fix that occurs during an import operation.
-
-  --skip-entries-publish
-      Skips entry publishing during the import process
-
-  --skip-existing
-      Skips the module exists warning messages.
-
-DESCRIPTION
-  Import content from a stack
-
-ALIASES
-  $ csdx cm:import
-
-EXAMPLES
-  $ csdx cm:stacks:import --stack-api-key <stack_api_key> --data-dir <path/of/export/destination/dir>
-
-  $ csdx cm:stacks:import --config <path/of/config/dir>
-
-  $ csdx cm:stacks:import --module <single module name>
-
-  $ csdx cm:stacks:import --module <single module name> --backup-dir <backup dir>
-
-  $ csdx cm:stacks:import --alias <management_token_alias>
-
-  $ csdx cm:stacks:import --alias <management_token_alias> --data-dir <path/of/export/destination/dir>
-
-  $ csdx cm:stacks:import --alias <management_token_alias> --config <path/of/config/file>
-
-  $ csdx cm:stacks:import --branch <branch name>  --yes --skip-audit
-```
-
-## `csdx cm:stacks:import-setup [-k <value>] [-d <value>] [-a <value>] [--modules <value,value>]`
-
-Helps to generate mappers and backup folder for importing (overwriting) specific modules
-
-```
-USAGE
-  $ csdx cm:import-setup cm:stacks:import-setup [-k <value>] [-d <value>] [-a <value>] [--modules <value,value>]
-
-FLAGS
-  -B, --branch=<value>         The name of the branch where you want to import your content. If you don't mention the
-                               branch name, then by default the content will be imported to the main branch.
-  -a, --alias=<value>          The management token of the destination stack where you will import the content.
-  -d, --data-dir=<value>       The path or the location in your file system where the content, you intend to import, is
-                               stored. For example, -d "C:\Users\Name\Desktop\cli\content". If the export folder has
-                               branches involved, then the path should point till the particular branch. For example,
-                               “-d "C:\Users\Name\Desktop\cli\content\branch_name"
-  -k, --stack-api-key=<value>  API key of the target stack
-      --branch-alias=<value>   Specify the branch alias where you want to import your content. If not specified, the
-                               content is imported into the main branch by default.
-      --module=<option>...     [optional] Specify the modules/module to import into the target stack. currently options
-                               are global-fields, content-types, entries
-                               <options: global-fields|content-types|entries>
-
-DESCRIPTION
-  Helps to generate mappers and backup folder for importing (overwriting) specific modules
-
-ALIASES
-  $ csdx cm:import-setup
-
-EXAMPLES
-  $ csdx cm:stacks:import-setup --stack-api-key <target_stack_api_key> --data-dir <path/of/export/destination/dir> --modules <module_name, module_name>
-
-  $ csdx cm:stacks:import-setup -k <target_stack_api_key> -d <path/of/export/destination/dir> --modules <module_name, module_name>
-
-  $ csdx cm:stacks:import-setup -k <target_stack_api_key> -d <path/of/export/destination/dir> --modules <module_name, module_name> -b <branch_name>
-```
-
-## `csdx cm:stacks:migration [-k <value>] [-a <value>] [--file-path <value>] [--branch <value>] [--config-file <value>] [--config <value>] [--multiple]`
-
-Contentstack migration script.
-
-```
-USAGE
-  $ csdx cm:migration cm:stacks:migration [-k <value>] [-a <value>] [--file-path <value>] [--branch <value>]
-    [--config-file <value>] [--config <value>] [--multiple]
-
-FLAGS
-  -B, --branch=<value>         Use this flag to add the branch name where you want to perform the migration. (target
-                               branch name)
-  -a, --alias=<value>          Use this flag to add the management token alias. You must use either the --alias flag or
-                               the --stack-api-key flag.
-  -k, --stack-api-key=<value>  Use this flag to add the API key of your stack. You must use either the --stack-api-key
-                               flag or the --alias flag.
-      --config=<value>...      [optional] Inline configuration, <key1>:<value1>. Passing an external configuration makes
-                               the script re-usable.
-      --config-file=<value>    [optional] Path of the JSON configuration file.
-      --file-path=<value>      Use this flag to provide the path of the file of the migration script.
-      --multiple               This flag helps you to migrate multiple content files in a single instance. Mention the
-                               folder path where your migration script files are stored.
-
-DESCRIPTION
-  Contentstack migration script.
-
-ALIASES
-  $ csdx cm:migration
-
-EXAMPLES
-  $ csdx cm:migration --file-path <migration/script/file/path> -k <api-key>
-
-  $ csdx cm:migration --file-path <migration/script/file/path> -k <api-key> --branch <target branch name>
-
-  $ csdx cm:migration --config <key1>:<value1> <key2>:<value2> ... --file-path <migration/script/file/path>
-
-  $ csdx cm:migration --config-file <path/to/json/config/file> --file-path <migration/script/file/path>
-
-  $ csdx cm:migration --multiple --file-path <migration/scripts/dir/path> 
-
-  $ csdx cm:migration --alias --file-path <migration/script/file/path> -k <api-key>
-```
-
-## `csdx cm:stacks:seed [--repo <value>] [--org <value>] [-k <value>] [-n <value>] [-y] [-s <value>] [--locale <value>]`
-
-Create a stack from existing content types, entries, assets, etc
-
-```
-USAGE
-  $ csdx cm:seed cm:stacks:seed [--repo <value>] [--org <value>] [-k <value>] [-n <value>] [-y] [-s <value>]
-    [--locale <value>]
-
-FLAGS
-  -a, --alias=<value>          Alias of the management token
-  -k, --stack-api-key=<value>  Provide stack API key to seed content to
-  -n, --stack-name=<value>     Name of a new stack that needs to be created.
-  -o, --org=<value>            Provide Organization UID to create a new stack
-  -r, --repo=<value>           GitHub organization name or GitHub user name/repository name.
-  -s, --stack=<value>          Provide the stack UID to seed content.
-  -y, --yes                    [Optional] Skip the stack confirmation.
-
-DESCRIPTION
-  Create a stack from existing content types, entries, assets, etc
-
-ALIASES
-  $ csdx cm:seed
-
-EXAMPLES
-  $ csdx cm:stacks:seed
-
-  $ csdx cm:stacks:seed --repo "account"
-
-  $ csdx cm:stacks:seed --repo "account/repository"
-
-  $ csdx cm:stacks:seed --repo "account/repository" --stack-api-key "stack-api-key" //seed content into specific stack
-
-  $ csdx cm:stacks:seed --repo "account/repository" --org "your-org-uid" --stack-name "stack-name" //create a new stack in given org uid
-```
-
-## `csdx cm:stacks:clone [--source-branch <value>] [--target-branch <value>] [--source-management-token-alias <value>] [--destination-management-token-alias <value>] [-n <value>] [--type a|b] [--source-stack-api-key <value>] [--destination-stack-api-key <value>] [--import-webhook-status disable|current]`
-
-Clone data (structure/content or both) of a stack into another stack
-
-```
-USAGE
-  $ csdx cm:stack-clone cm:stacks:clone [--source-branch <value>] [--target-branch <value>]
-    [--source-management-token-alias <value>] [--destination-management-token-alias <value>] [-n <value>] [--type a|b]
-    [--source-stack-api-key <value>] [--destination-stack-api-key <value>] [--import-webhook-status disable|current]
-
-FLAGS
-  -c, --config=<value>                              Path for the external configuration
-  -n, --stack-name=<value>                          Provide a name for the new stack to store the cloned content.
-  -y, --yes                                         Force override all Marketplace prompts.
-      --destination-management-token-alias=<value>  Destination management token alias.
-      --destination-stack-api-key=<value>           Destination stack API key
-      --import-webhook-status=<option>              [default: disable] [default: disable] (optional) The status of the
-                                                    import webhook. <options: disable|current>
-                                                    <options: disable|current>
-      --skip-audit                                  (optional) Skips the audit fix that occurs during an import
-                                                    operation.
-      --source-branch=<value>                       Branch of the source stack.
-      --source-branch-alias=<value>                 Alias of Branch of the source stack.
-      --source-management-token-alias=<value>       Source management token alias.
-      --source-stack-api-key=<value>                Source stack API key
-      --target-branch=<value>                       Branch of the target stack.
-      --target-branch-alias=<value>                 Alias of Branch of the target stack.
-      --type=<option>                               Type of data to clone. You can select option a or b.
-                                                    a) Structure (all modules except entries & assets).
-                                                    b) Structure with content (all modules including entries & assets).
-
-                                                    <options: a|b>
-
-DESCRIPTION
-  Clone data (structure/content or both) of a stack into another stack
-  Use this plugin to automate the process of cloning a stack in few steps.
-
-
-ALIASES
-  $ csdx cm:stack-clone
-
-EXAMPLES
-  $ csdx cm:stacks:clone
-
-  $ csdx cm:stacks:clone --source-branch <source-branch-name> --target-branch <target-branch-name> --yes
-
-  $ csdx cm:stacks:clone --source-stack-api-key <apiKey> --destination-stack-api-key <apiKey>
-
-  $ csdx cm:stacks:clone --source-management-token-alias <management token alias> --destination-management-token-alias <management token alias>
-
-  $ csdx cm:stacks:clone --source-branch --target-branch --source-management-token-alias <management token alias> --destination-management-token-alias <management token alias>
-
-  $ csdx cm:stacks:clone --source-branch --target-branch --source-management-token-alias <management token alias> --destination-management-token-alias <management token alias> --type <value a or b>
-```
-
-## `csdx cm:stacks:audit`
-
-Perform audits and find possible errors in the exported Contentstack data
-
-```
-USAGE
-  $ csdx cm:stacks:audit [-c <value>] [-d <value>] [--show-console-output] [--report-path <value>] [--modules
-    content-types|global-fields|entries|extensions|workflows|custom-roles|assets|field-rules|composable-studio...]
-    [--columns <value>] [--sort <value>] [--filter <value>] [--csv] [--no-truncate] [--no-header] [--output
-    csv|json|yaml]
-
-FLAGS
-  --modules=<option>...  Provide the list of modules to be audited
-                         <options: content-types|global-fields|entries|extensions|workflows|custom-roles|assets|field-ru
-                         les|composable-studio>
-  --report-path=<value>  Path to store the audit reports
-
-COMMON FLAGS
-  -c, --config=<value>       Path of the external config
-  -d, --data-dir=<value>     Path where the data is stored
-      --show-console-output  Display the audit and audit fix result for individual modules
-
-TABLE FLAGS
-  --columns=<value>  Specify columns to display, comma-separated.
-  --csv              Output results in CSV format.
-  --filter=<value>   Filter rows by a column value (e.g., name=foo).
-  --no-header        Hide table headers in output.
-  --no-truncate      Prevent truncation of long text in columns.
-  --output=<option>  Specify output format: csv, json, or yaml.
-                     <options: csv|json|yaml>
-  --sort=<value>     Sort the table by a column. Use "-" for descending.
-
-DESCRIPTION
-  Perform audits and find possible errors in the exported Contentstack data
-
-ALIASES
-  $ csdx audit
-  $ csdx cm:stacks:audit
-
-EXAMPLES
-  $ csdx cm:stacks:audit
-
-  $ csdx cm:stacks:audit --report-path=<path>
-
-  $ csdx cm:stacks:audit --report-path=<path> --csv
-
-  $ csdx cm:stacks:audit --report-path=<path> --filter="name=<filter-value>"
-
-  $ csdx cm:stacks:audit --report-path=<path> --modules=content-types --filter="name="<filter-value>"
-```
-
-_See code: [@contentstack/cli-audit](https://github.com/contentstack/audit/blob/main/packages/contentstack-audit/src/commands/cm/stacks/audit/index.ts)_
-
-## `csdx cm:stacks:audit:fix`
-
-Perform audits and fix possible errors in the exported Contentstack data.
-
-```
-USAGE
-  $ csdx cm:stacks:audit:fix [-c <value>] [-d <value>] [--show-console-output] [--report-path <value>] [--modules
-    content-types|global-fields|entries|extensions|workflows|custom-roles|assets|field-rules|composable-studio...]
-    [--copy-path <value> --copy-dir] [--fix-only
-    reference|global_field|json:rte|json:extension|blocks|group|content_types...] [--columns <value>] [--sort <value>]
-    [--filter <value>] [--csv] [--no-truncate] [--no-header] [--output csv|json|yaml]
-
-FLAGS
-  --copy-dir              Create backup from the original data.
-  --copy-path=<value>     Provide the path to backup the copied data
-  --fix-only=<option>...  Provide the list of fix options
-                          <options: reference|global_field|json:rte|json:extension|blocks|group|content_types>
-  --modules=<option>...   Provide the list of modules to be audited
-                          <options: content-types|global-fields|entries|extensions|workflows|custom-roles|assets|field-r
-                          ules|composable-studio>
-  --report-path=<value>   Path to store the audit reports
-
-COMMON FLAGS
-  -c, --config=<value>       Path of the external config
-  -d, --data-dir=<value>     Path where the data is stored
-      --show-console-output  Display the audit and audit fix result for individual modules
-
-TABLE FLAGS
-  --columns=<value>  Specify columns to display, comma-separated.
-  --csv              Output results in CSV format.
-  --filter=<value>   Filter rows by a column value (e.g., name=foo).
-  --no-header        Hide table headers in output.
-  --no-truncate      Prevent truncation of long text in columns.
-  --output=<option>  Specify output format: csv, json, or yaml.
-                     <options: csv|json|yaml>
-  --sort=<value>     Sort the table by a column. Use "-" for descending.
-
-DESCRIPTION
-  Perform audits and fix possible errors in the exported Contentstack data.
-
-ALIASES
-  $ csdx audit:fix
-  $ csdx cm:stacks:audit:fix
-
-EXAMPLES
-  $ csdx cm:stacks:audit:fix --copy-dir
-
-  $ csdx cm:stacks:audit:fix --report-path=<path> --copy-dir
-
-  $ csdx cm:stacks:audit:fix --report-path=<path> --copy-dir --csv
-
-  $ csdx cm:stacks:audit:fix --fix-only=reference,global_field --copy-dir
-
-  $ csdx cm:stacks:audit:fix --report-path=<path> --filter="name=<filter-value>"
-
-  $ csdx cm:stacks:audit:fix --report-path=<path> --modules=content-types --filter="name="<filter-value>" --copy-dir --copy-path=<path>
-```
-
-_See code: [@contentstack/cli-audit](https://github.com/contentstack/audit/blob/main/packages/contentstack-audit/src/commands/cm/stacks/audit/fix.ts)_
-
-## `csdx cm:stacks:clone [--source-branch <value>] [--target-branch <value>] [--source-management-token-alias <value>] [--destination-management-token-alias <value>] [-n <value>] [--type a|b] [--source-stack-api-key <value>] [--destination-stack-api-key <value>] [--import-webhook-status disable|current]`
-
-Clone data (structure/content or both) of a stack into another stack
-
-```
-USAGE
-  $ csdx cm:stacks:clone [--source-branch <value>] [--target-branch <value>] [--source-management-token-alias
-    <value>] [--destination-management-token-alias <value>] [-n <value>] [--type a|b] [--source-stack-api-key <value>]
-    [--destination-stack-api-key <value>] [--import-webhook-status disable|current]
-
-FLAGS
-  -c, --config=<value>                              Path for the external configuration
-  -n, --stack-name=<value>                          Provide a name for the new stack to store the cloned content.
-  -y, --yes                                         Force override all Marketplace prompts.
-      --destination-management-token-alias=<value>  Destination management token alias.
-      --destination-stack-api-key=<value>           Destination stack API key
-      --import-webhook-status=<option>              [default: disable] [default: disable] (optional) The status of the
-                                                    import webhook. <options: disable|current>
-                                                    <options: disable|current>
-      --skip-audit                                  (optional) Skips the audit fix that occurs during an import
-                                                    operation.
-      --source-branch=<value>                       Branch of the source stack.
-      --source-branch-alias=<value>                 Alias of Branch of the source stack.
-      --source-management-token-alias=<value>       Source management token alias.
-      --source-stack-api-key=<value>                Source stack API key
-      --target-branch=<value>                       Branch of the target stack.
-      --target-branch-alias=<value>                 Alias of Branch of the target stack.
-      --type=<option>                               Type of data to clone. You can select option a or b.
-                                                    a) Structure (all modules except entries & assets).
-                                                    b) Structure with content (all modules including entries & assets).
-
-                                                    <options: a|b>
-
-DESCRIPTION
-  Clone data (structure/content or both) of a stack into another stack
-  Use this plugin to automate the process of cloning a stack in few steps.
-
-
-ALIASES
-  $ csdx cm:stack-clone
-
-EXAMPLES
-  $ csdx cm:stacks:clone
-
-  $ csdx cm:stacks:clone --source-branch <source-branch-name> --target-branch <target-branch-name> --yes
-
-  $ csdx cm:stacks:clone --source-stack-api-key <apiKey> --destination-stack-api-key <apiKey>
-
-  $ csdx cm:stacks:clone --source-management-token-alias <management token alias> --destination-management-token-alias <management token alias>
-
-  $ csdx cm:stacks:clone --source-branch --target-branch --source-management-token-alias <management token alias> --destination-management-token-alias <management token alias>
-
-  $ csdx cm:stacks:clone --source-branch --target-branch --source-management-token-alias <management token alias> --destination-management-token-alias <management token alias> --type <value a or b>
-```
-
-_See code: [@contentstack/cli-cm-clone](https://github.com/contentstack/cli/blob/main/packages/contentstack-clone/src/commands/cm/stacks/clone.ts)_
-
-## `csdx cm:stacks:export [-c <value>] [-k <value>] [-d <value>] [-a <value>] [--module <value>] [--content-types <value>] [--branch <value>] [--secured-assets]`
-
-Export content from a stack
-
-```
-USAGE
-  $ csdx cm:stacks:export [-c <value>] [-k <value>] [-d <value>] [-a <value>] [--module <value>] [--content-types
-    <value>] [--branch <value>] [--secured-assets]
-
-FLAGS
-  -B, --branch=<value>            [optional] The name of the branch where you want to export your content. If you don't
-                                  mention the branch name, then by default the content will be exported from all the
-                                  branches of your stack.
-  -a, --alias=<value>             The management token alias of the source stack from which you will export content.
-  -c, --config=<value>            [optional] Path of the config
-  -d, --data-dir=<value>          The path or the location in your file system to store the exported content. For e.g.,
-                                  ./content
-  -k, --stack-api-key=<value>     API Key of the source stack
-  -m, --module=<value>            [optional] Specific module name. If not specified, the export command will export all
-                                  the modules to the stack. The available modules are assets, content-types, entries,
-                                  environments, extensions, marketplace-apps, global-fields, labels, locales, webhooks,
-                                  workflows, custom-roles, taxonomies, and studio.
-  -t, --content-types=<value>...  [optional]  The UID of the content type(s) whose content you want to export. In case
-                                  of multiple content types, specify the IDs separated by spaces.
-  -y, --yes                       [optional] Force override all Marketplace prompts.
-      --branch-alias=<value>      (Optional) The alias of the branch from which you want to export content.
-      --secured-assets            [optional] Use this flag for assets that are secured.
-
-DESCRIPTION
-  Export content from a stack
-
-ALIASES
-  $ csdx cm:export
-
-EXAMPLES
-  $ csdx cm:stacks:export --stack-api-key <stack_api_key> --data-dir <path/of/export/destination/dir>
-
-  $ csdx cm:stacks:export --config <path/to/config/dir>
-
-  $ csdx cm:stacks:export --alias <management_token_alias>
-
-  $ csdx cm:stacks:export --alias <management_token_alias> --data-dir <path/to/export/destination/dir>
-
-  $ csdx cm:stacks:export --alias <management_token_alias> --config <path/to/config/file>
-
-  $ csdx cm:stacks:export --module <single module name>
-
-  $ csdx cm:stacks:export --branch [optional] branch name
-```
-
-_See code: [@contentstack/cli-cm-export](https://github.com/contentstack/cli/blob/main/packages/contentstack-export/src/commands/cm/stacks/export.ts)_
-
-## `csdx cm:stacks:import [-c <value>] [-k <value>] [-d <value>] [-a <value>] [--module <value>] [--backup-dir <value>] [--branch <value>] [--import-webhook-status disable|current]`
-
-Import content from a stack
-
-```
-USAGE
-  $ csdx cm:stacks:import [-c <value>] [-k <value>] [-d <value>] [-a <value>] [--module <value>] [--backup-dir
-    <value>] [--branch <value>] [--import-webhook-status disable|current]
-
-FLAGS
-  -B, --branch=<value>
-      The name of the branch where you want to import your content. If you don't mention the branch name, then by default
-      the content will be imported to the main branch.
-
-  -a, --alias=<value>
-      The management token of the destination stack where you will import the content.
-
-  -b, --backup-dir=<value>
-      [optional] Backup directory name when using specific module.
-
-  -c, --config=<value>
-      [optional] The path of the configuration JSON file containing all the options for a single run.
-
-  -d, --data-dir=<value>
-      The path or the location in your file system where the content, you intend to import, is stored. For example, -d
-      "C:\Users\Name\Desktop\cli\content". If the export folder has branches involved, then the path should point till the
-      particular branch. For example, “-d "C:\Users\Name\Desktop\cli\content\branch_name"
-
-  -k, --stack-api-key=<value>
-      API Key of the target stack
-
-  -m, --module=<value>
-      [optional] Specify the module to import into the target stack. If not specified, the import command will import all
-      the modules into the stack. The available modules are assets, content-types, entries, environments, extensions,
-      marketplace-apps, global-fields, labels, locales, webhooks, workflows, custom-roles, personalize projects,
-      taxonomies, and composable-studio.
-
-  -y, --yes
-      [optional] Force override all Marketplace prompts.
-
-  --branch-alias=<value>
-      Specify the branch alias where you want to import your content. If not specified, the content is imported into the
-      main branch by default.
-
-  --exclude-global-modules
-      Excludes the branch-independent module from the import operation.
-
-  --import-webhook-status=<option>
-      [default: disable] [default: disable] (optional) This webhook state keeps the same state of webhooks as the source
-      stack. <options: disable|current>
-      <options: disable|current>
-
-  --personalize-project-name=<value>
-      (optional) Provide a unique name for the Personalize project.
-
-  --replace-existing
-      Replaces the existing module in the target stack.
-
-  --skip-app-recreation
-      (optional) Skips the recreation of private apps if they already exist.
-
-  --skip-assets-publish
-      Skips asset publishing during the import process.
-
-  --skip-audit
-      Skips the audit fix that occurs during an import operation.
-
-  --skip-entries-publish
-      Skips entry publishing during the import process
-
-  --skip-existing
-      Skips the module exists warning messages.
-
-DESCRIPTION
-  Import content from a stack
-
-ALIASES
-  $ csdx cm:import
-
-EXAMPLES
-  $ csdx cm:stacks:import --stack-api-key <stack_api_key> --data-dir <path/of/export/destination/dir>
-
-  $ csdx cm:stacks:import --config <path/of/config/dir>
-
-  $ csdx cm:stacks:import --module <single module name>
-
-  $ csdx cm:stacks:import --module <single module name> --backup-dir <backup dir>
-
-  $ csdx cm:stacks:import --alias <management_token_alias>
-
-  $ csdx cm:stacks:import --alias <management_token_alias> --data-dir <path/of/export/destination/dir>
-
-  $ csdx cm:stacks:import --alias <management_token_alias> --config <path/of/config/file>
-
-  $ csdx cm:stacks:import --branch <branch name>  --yes --skip-audit
-```
-
-_See code: [@contentstack/cli-cm-import](https://github.com/contentstack/cli/blob/main/packages/contentstack-import/src/commands/cm/stacks/import.ts)_
-
-## `csdx cm:stacks:import-setup [-k <value>] [-d <value>] [-a <value>] [--modules <value,value>]`
-
-Helps to generate mappers and backup folder for importing (overwriting) specific modules
-
-```
-USAGE
-  $ csdx cm:stacks:import-setup [-k <value>] [-d <value>] [-a <value>] [--modules <value,value>]
-
-FLAGS
-  -B, --branch=<value>         The name of the branch where you want to import your content. If you don't mention the
-                               branch name, then by default the content will be imported to the main branch.
-  -a, --alias=<value>          The management token of the destination stack where you will import the content.
-  -d, --data-dir=<value>       The path or the location in your file system where the content, you intend to import, is
-                               stored. For example, -d "C:\Users\Name\Desktop\cli\content". If the export folder has
-                               branches involved, then the path should point till the particular branch. For example,
-                               “-d "C:\Users\Name\Desktop\cli\content\branch_name"
-  -k, --stack-api-key=<value>  API key of the target stack
-      --branch-alias=<value>   Specify the branch alias where you want to import your content. If not specified, the
-                               content is imported into the main branch by default.
-      --module=<option>...     [optional] Specify the modules/module to import into the target stack. currently options
-                               are global-fields, content-types, entries
-                               <options: global-fields|content-types|entries>
-
-DESCRIPTION
-  Helps to generate mappers and backup folder for importing (overwriting) specific modules
-
-ALIASES
-  $ csdx cm:import-setup
-
-EXAMPLES
-  $ csdx cm:stacks:import-setup --stack-api-key <target_stack_api_key> --data-dir <path/of/export/destination/dir> --modules <module_name, module_name>
-
-  $ csdx cm:stacks:import-setup -k <target_stack_api_key> -d <path/of/export/destination/dir> --modules <module_name, module_name>
-
-  $ csdx cm:stacks:import-setup -k <target_stack_api_key> -d <path/of/export/destination/dir> --modules <module_name, module_name> -b <branch_name>
-```
-
-_See code: [@contentstack/cli-cm-import-setup](https://github.com/contentstack/cli/blob/main/packages/contentstack-import-setup/src/commands/cm/stacks/import-setup.ts)_
-
-## `csdx cm:stacks:migration [-k <value>] [-a <value>] [--file-path <value>] [--branch <value>] [--config-file <value>] [--config <value>] [--multiple]`
-
-Contentstack migration script.
-
-```
-USAGE
-  $ csdx cm:stacks:migration [-k <value>] [-a <value>] [--file-path <value>] [--branch <value>] [--config-file <value>]
-    [--config <value>] [--multiple]
-
-FLAGS
-  -B, --branch=<value>         Use this flag to add the branch name where you want to perform the migration. (target
-                               branch name)
-  -a, --alias=<value>          Use this flag to add the management token alias. You must use either the --alias flag or
-                               the --stack-api-key flag.
-  -k, --stack-api-key=<value>  Use this flag to add the API key of your stack. You must use either the --stack-api-key
-                               flag or the --alias flag.
-      --config=<value>...      [optional] Inline configuration, <key1>:<value1>. Passing an external configuration makes
-                               the script re-usable.
-      --config-file=<value>    [optional] Path of the JSON configuration file.
-      --file-path=<value>      Use this flag to provide the path of the file of the migration script.
-      --multiple               This flag helps you to migrate multiple content files in a single instance. Mention the
-                               folder path where your migration script files are stored.
-
-DESCRIPTION
-  Contentstack migration script.
-
-ALIASES
-  $ csdx cm:migration
-
-EXAMPLES
-  $ csdx cm:migration --file-path <migration/script/file/path> -k <api-key>
-
-  $ csdx cm:migration --file-path <migration/script/file/path> -k <api-key> --branch <target branch name>
-
-  $ csdx cm:migration --config <key1>:<value1> <key2>:<value2> ... --file-path <migration/script/file/path>
-
-  $ csdx cm:migration --config-file <path/to/json/config/file> --file-path <migration/script/file/path>
-
-  $ csdx cm:migration --multiple --file-path <migration/scripts/dir/path> 
-
-  $ csdx cm:migration --alias --file-path <migration/script/file/path> -k <api-key>
-```
-
-_See code: [@contentstack/cli-migration](https://github.com/contentstack/cli/blob/main/packages/contentstack-migration/src/commands/cm/stacks/migration.ts)_
-
-## `csdx cm:stacks:publish`
-
-Publish entries and assets to multiple environments and locales
-
-```
-USAGE
-  $ csdx cm:stacks:publish
-
-DESCRIPTION
-  Publish entries and assets to multiple environments and locales
-  The publish command is used to publish entries and assets, to the specified environments and locales.
-
-  Note: Content types, Environments and Locales are required to execute the publish entries command successfully.
-  Note: Environments and Locales are required to execute the publish assets command successfully.
-  But, if retry-failed flag is set, then only a logfile is required
-
-EXAMPLES
-  General Usage
-
-  $ csdx cm:stacks:publish --environments [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE] --alias [MANAGEMENT TOKEN ALIAS]
-
-
-
-  Using --config or -c flag
-
-  Generate a config file in the current working directory using `csdx cm:stacks:publish-configure -a [ALIAS]`
-
-  $ csdx cm:stacks:publish --config [PATH TO CONFIG FILE]
-
-  $ csdx cm:stacks:publish -c [PATH TO CONFIG FILE]
-
-
-
-  Using --retry-failed flag
-
-  $ csdx cm:stacks:publish --retry-failed [LOG FILE NAME]
-
-
-
-  Using --branch flag
-
-  $ csdx cm:stacks:publish --environments [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE] --alias [MANAGEMENT TOKEN ALIAS] --branch [BRANCH NAME]
-
-
-
-  Using --api-version flag
-
-  $ csdx cm:stacks:publish --environments [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE] --alias [MANAGEMENT TOKEN ALIAS] --api-version [API VERSION]
-```
-
-_See code: [@contentstack/cli-cm-bulk-publish](https://github.com/contentstack/cli/blob/main/packages/contentstack-bulk-publish/src/commands/cm/stacks/publish.js)_
-
-## `csdx cm:stacks:publish-clear-logs`
-
-Clear the log folder
-
-```
-USAGE
-  $ csdx cm:stacks:publish-clear-logs [--log-files-count] [-y]
-
-FLAGS
-  -y, --yes              Delete all files without asking for confirmation
-      --log-files-count  List number of log files
-
-DESCRIPTION
-  Clear the log folder
-
-ALIASES
-  $ csdx cm:bulk-publish:clear
-
-EXAMPLES
-  $ csdx cm:stacks:publish-clear-logs
-
-  $ csdx cm:stacks:publish-clear-logs --log-files-count
-
-  $ csdx cm:stacks:publish-clear-logs --yes
-
-  $ csdx cm:stacks:publish-clear-logs -y
-```
-
-_See code: [@contentstack/cli-cm-bulk-publish](https://github.com/contentstack/cli/blob/main/packages/contentstack-bulk-publish/src/commands/cm/stacks/publish-clear-logs.js)_
-
-## `csdx cm:stacks:publish-configure`
-
-The configure command is used to generate a configuration file for publish scripts.
-
-```
-USAGE
-  $ csdx cm:stacks:publish-configure [-a <value>] [-k <value>]
-
-FLAGS
-  -a, --alias=<value>          Name (alias) of the management token you want to use. You must use either the --alias
-                               flag or the --stack-api-key flag.
-  -k, --stack-api-key=<value>  API key of the source stack. You must use either the --stack-api-key flag or the --alias
-                               flag.
-
-DESCRIPTION
-  The configure command is used to generate a configuration file for publish scripts.
-
-ALIASES
-  $ csdx cm:bulk-publish:configure
-
-EXAMPLES
-  $ csdx cm:stacks:publish-configure
-
-  $ csdx cm:stacks:publish-configure -a <management_token_alias>
-
-  $ csdx cm:stacks:publish-configure --alias <management_token_alias>
-
-  $ csdx cm:stacks:publish-configure --stack-api-key <stack_api_key>
-```
-
-_See code: [@contentstack/cli-cm-bulk-publish](https://github.com/contentstack/cli/blob/main/packages/contentstack-bulk-publish/src/commands/cm/stacks/publish-configure.js)_
-
-## `csdx cm:stacks:publish-revert`
-
-Revert publish operations by using a log file
-
-```
-USAGE
-  $ csdx cm:stacks:publish-revert [--retry-failed <value>] [--log-file <value>]
-
-FLAGS
-  --log-file=<value>      Path of the success logfile of a particular publish action.
-  --retry-failed=<value>  (optional)  Use this option to retry publishing the failed entries from the logfile. Specify
-                          the name of the logfile that lists failed publish calls. If this option is used, it will
-                          override all other flags.
-
-DESCRIPTION
-  Revert publish operations by using a log file
-  The revert command is used to revert all publish operations performed using bulk-publish script.
-  A log file name is required to execute revert command
-
-
-ALIASES
-  $ csdx cm:bulk-publish:revert
-
-EXAMPLES
-  Using --log-file
-
-  cm:bulk-publish:revert --log-file [LOG FILE NAME]
-
-
-
-  Using --retry-failed
-
-  cm:bulk-publish:revert --retry-failed [LOG FILE NAME]
-```
-
-_See code: [@contentstack/cli-cm-bulk-publish](https://github.com/contentstack/cli/blob/main/packages/contentstack-bulk-publish/src/commands/cm/stacks/publish-revert.js)_
-
-## `csdx cm:stacks:seed [--repo <value>] [--org <value>] [-k <value>] [-n <value>] [-y] [-s <value>] [--locale <value>]`
-
-Create a stack from existing content types, entries, assets, etc
-
-```
-USAGE
-  $ csdx cm:stacks:seed [--repo <value>] [--org <value>] [-k <value>] [-n <value>] [-y] [-s <value>] [--locale
-    <value>]
-
-FLAGS
-  -a, --alias=<value>          Alias of the management token
-  -k, --stack-api-key=<value>  Provide stack API key to seed content to
-  -n, --stack-name=<value>     Name of a new stack that needs to be created.
-  -o, --org=<value>            Provide Organization UID to create a new stack
-  -r, --repo=<value>           GitHub organization name or GitHub user name/repository name.
-  -s, --stack=<value>          Provide the stack UID to seed content.
-  -y, --yes                    [Optional] Skip the stack confirmation.
-
-DESCRIPTION
-  Create a stack from existing content types, entries, assets, etc
-
-ALIASES
-  $ csdx cm:seed
-
-EXAMPLES
-  $ csdx cm:stacks:seed
-
-  $ csdx cm:stacks:seed --repo "account"
-
-  $ csdx cm:stacks:seed --repo "account/repository"
-
-  $ csdx cm:stacks:seed --repo "account/repository" --stack-api-key "stack-api-key" //seed content into specific stack
-
-  $ csdx cm:stacks:seed --repo "account/repository" --org "your-org-uid" --stack-name "stack-name" //create a new stack in given org uid
-```
-
-_See code: [@contentstack/cli-cm-seed](https://github.com/contentstack/cli/blob/main/packages/contentstack-seed/src/commands/cm/stacks/seed.ts)_
-
-## `csdx csdx cm:stacks:unpublish [-a <value>] [-e <value>] [-c <value>] [-y] [--locale <value>] [--branch <value>] [--retry-failed <value>] [--bulk-unpublish <value>] [--content-type <value>] [--delivery-token <value>] [--only-assets] [--only-entries]`
-
-Unpublish entries or assets of given content types from the specified environment
-
-```
-USAGE
-  $ csdx cm:stacks:unpublish csdx cm:stacks:unpublish [-a <value>] [-e <value>] [-c <value>] [-y] [--locale <value>]
-    [--branch <value>] [--retry-failed <value>] [--bulk-unpublish <value>] [--content-type <value>] [--delivery-token
-    <value>] [--only-assets] [--only-entries]
-
-FLAGS
-  -B, --branch=<value>          [default: main] Specify the branch to fetch the content from (default is main branch)
-  -a, --alias=<value>           Alias(name) for the management token
-  -c, --config=<value>          Path to the config file
-  -e, --environment=<value>     Source Environment
-  -k, --stack-api-key=<value>   Stack API key to be used
-  -l, --locale=<value>          Locale filter
-  -y, --yes                     Agree to process the command with the current configuration
-      --api-version=<value>     API version to be used. Values [Default: 3, Nested Reference Publishing: 3.2].
-      --bulk-unpublish=<value>  [default: true] This flag is set to true by default. It indicates that contentstack's
-                                bulkpublish API will be used to unpublish the entries and assets
-      --content-type=<value>    Content type filter
-      --delivery-token=<value>  The delivery token of the source environment.
-      --retry-failed=<value>    Retry publishing failed entries from the logfile (optional, overrides all other flags)
-
-DESCRIPTION
-  Unpublish entries or assets of given content types from the specified environment
-  The unpublish command is used to unpublish entries or assets from given environment
-
-  Environment (Source Environment) and Locale are required to execute the command successfully
-  But, if retry-failed flag is set, then only a logfile is required
-
-  A content type can be specified for unpublishing entries, but if no content-type(s) is/are specified and --only-assets
-  is not used,
-  then all entries from all content types will be unpublished from the source environment
-
-  Note: --only-assets can be used to unpublish only assets and --only-entries can be used to unpublish only entries.
-  (--only-assets and --only-entries cannot be used together at the same time)
-
-
-ALIASES
-  $ csdx cm:bulk-publish:unpublish
-
-EXAMPLES
-  General Usage
-
-  $ csdx cm:stacks:unpublish --bulk-unpublish --content-type [CONTENT TYPE] --environment [SOURCE ENV] --locale [LOCALE] --alias [MANAGEMENT TOKEN ALIAS] ----delivery-token [DELIVERY TOKEN]
-
-
-
-  Using --config or -c flag
-
-  Generate a config file at the current working directory using `csdx cm:bulk-publish:configure --alias [ALIAS]`
-
-  $ csdx cm:stacks:unpublish --config [PATH TO CONFIG FILE]
-
-  $ csdx cm:stacks:unpublish -c [PATH TO CONFIG FILE]
-
-
-
-  Using --retry-failed flag
-
-  $ csdx cm:stacks:unpublish --retry-failed [LOG FILE NAME]
-
-
-
-  No content type
-
-  $ csdx cm:stacks:unpublish --environment [SOURCE ENV] --locale [LOCALE] (Will unpublish all entries from all content types and assets from the source environment)
-
-
-
-  Using --only-assets
-
-  $ csdx cm:stacks:unpublish --environment [SOURCE ENV] --locale [LOCALE] --only-assets (Will unpublish only assets from the source environment)
-
-
-
-  Using --only-entries
-
-  $ csdx cm:stacks:unpublish --environment [SOURCE ENV] --locale [LOCALE] --only-entries (Will unpublish only entries, all entries, from the source environment)
-
-  $ csdx cm:stacks:unpublish --contentType [CONTENT TYPE] --environment [SOURCE ENV] --locale [LOCALE] --only-entries (Will unpublish only entries, (from CONTENT TYPE) from the source environment)
-
-
-
-  Using --branch flag
-
-  $ csdx cm:stacks:unpublish --bulk-unpublish --content-type [CONTENT TYPE] --environment [SOURCE ENV] --locale [LOCALE] --alias [MANAGEMENT TOKEN ALIAS] --delivery-token [DELIVERY TOKEN] --branch [BRANCH NAME]
-
-
-
-  Using --stack-api-key flag
-
-  $ csdx cm:stacks:unpublish --bulk-unpublish --content-type [CONTENT TYPE] --environment [SOURCE ENV] --locale [LOCALE] --stack-api-key [STACK API KEY] --delivery-token [DELIVERY TOKEN]
-```
-
-_See code: [@contentstack/cli-cm-bulk-publish](https://github.com/contentstack/cli/blob/main/packages/contentstack-bulk-publish/src/commands/cm/stacks/unpublish.js)_
-
-## `csdx config:get:base-branch`
-
-Get current branch set for CLI
-
-```
-USAGE
-  $ csdx config:get:base-branch
-
-DESCRIPTION
-  Get current branch set for CLI
-
-EXAMPLES
-  $ csdx config:get:base-branch
-```
-
-_See code: [@contentstack/cli-config](https://github.com/contentstack/cli/blob/main/packages/contentstack-config/src/commands/config/get/base-branch.ts)_
-
-## `csdx config:get:ea-header`
-
-Display Early Access headers
-
-```
-USAGE
-  $ csdx config:get:ea-header
-
-DESCRIPTION
-  Display Early Access headers
-
-ALIASES
-  $ csdx config:get:ea-header
-
-EXAMPLES
-  $ csdx config:get:ea-header
-```
-
-## `csdx config:get:early-access-header`
-
-Display Early Access headers
-
-```
-USAGE
-  $ csdx config:get:early-access-header
-
-DESCRIPTION
-  Display Early Access headers
-
-ALIASES
-  $ csdx config:get:ea-header
-
-EXAMPLES
-  $ csdx config:get:early-access-header
-```
-
-_See code: [@contentstack/cli-config](https://github.com/contentstack/cli/blob/main/packages/contentstack-config/src/commands/config/get/early-access-header.ts)_
-
-## `csdx config:get:log`
-
-Get logging configuration for CLI
-
-```
-USAGE
-  $ csdx config:get:log
-
-DESCRIPTION
-  Get logging configuration for CLI
-
-EXAMPLES
-  $ csdx config:get:log
-```
-
-_See code: [@contentstack/cli-config](https://github.com/contentstack/cli/blob/main/packages/contentstack-config/src/commands/config/get/log.ts)_
-
-## `csdx config:get:proxy`
-
-Get proxy configuration for CLI
-
-```
-USAGE
-  $ csdx config:get:proxy
-
-DESCRIPTION
-  Get proxy configuration for CLI
-
-EXAMPLES
-  $ csdx config:get:proxy
-```
-
-_See code: [@contentstack/cli-config](https://github.com/contentstack/cli/blob/main/packages/contentstack-config/src/commands/config/get/proxy.ts)_
-
-## `csdx config:get:rate-limit`
-
-Get rate-limit of organizations
-
-```
-USAGE
-  $ csdx config:get:rate-limit
-
-DESCRIPTION
-  Get rate-limit of organizations
-
-EXAMPLES
-  $ csdx config:get:rate-limit
-```
-
-_See code: [@contentstack/cli-config](https://github.com/contentstack/cli/blob/main/packages/contentstack-config/src/commands/config/get/rate-limit.ts)_
-
-## `csdx config:get:region`
-
-Get current region set for CLI
-
-```
-USAGE
-  $ csdx config:get:region
-
-DESCRIPTION
-  Get current region set for CLI
-
-EXAMPLES
-  $ csdx config:get:region
-```
-
-_See code: [@contentstack/cli-config](https://github.com/contentstack/cli/blob/main/packages/contentstack-config/src/commands/config/get/region.ts)_
-
-## `csdx config:remove:base-branch`
-
-Remove branch config for CLI
-
-```
-USAGE
-  $ csdx config:remove:base-branch [-k <value>] [-y]
-
-FLAGS
-  -k, --stack-api-key=<value>  Stack API key.
-  -y, --yes                    Force remove.
-
-DESCRIPTION
-  Remove branch config for CLI
-
-EXAMPLES
-  $ csdx config:remove:base-branch
-
-  $ csdx config:remove:base-branch --stack-api-key <value>
-```
-
-_See code: [@contentstack/cli-config](https://github.com/contentstack/cli/blob/main/packages/contentstack-config/src/commands/config/remove/base-branch.ts)_
-
-## `csdx config:remove:ea-header`
-
-Remove Early Access header
-
-```
-USAGE
-  $ csdx config:remove:ea-header [--header-alias <value>] [-y]
-
-FLAGS
-  -y, --yes                   (optional) Force the removal of Early Access header configuration by skipping the
-                              confirmation.
-      --header-alias=<value>  (optional) Provide the Early Access header alias name.
-
-DESCRIPTION
-  Remove Early Access header
-
-ALIASES
-  $ csdx config:remove:ea-header
-
-EXAMPLES
-  $ csdx config:remove:ea-header
-
-  $ csdx config:remove:ea-header --header-alias <value>
-```
-
-## `csdx config:remove:early-access-header`
-
-Remove Early Access header
-
-```
-USAGE
-  $ csdx config:remove:early-access-header [--header-alias <value>] [-y]
-
-FLAGS
-  -y, --yes                   (optional) Force the removal of Early Access header configuration by skipping the
-                              confirmation.
-      --header-alias=<value>  (optional) Provide the Early Access header alias name.
-
-DESCRIPTION
-  Remove Early Access header
-
-ALIASES
-  $ csdx config:remove:ea-header
-
-EXAMPLES
-  $ csdx config:remove:early-access-header
-
-  $ csdx config:remove:early-access-header --header-alias <value>
-```
-
-_See code: [@contentstack/cli-config](https://github.com/contentstack/cli/blob/main/packages/contentstack-config/src/commands/config/remove/early-access-header.ts)_
-
-## `csdx config:remove:proxy`
-
-Remove proxy configuration from global config
-
-```
-USAGE
-  $ csdx config:remove:proxy
-
-DESCRIPTION
-  Remove proxy configuration from global config
-
-EXAMPLES
-  $ csdx config:remove:proxy
-```
-
-_See code: [@contentstack/cli-config](https://github.com/contentstack/cli/blob/main/packages/contentstack-config/src/commands/config/remove/proxy.ts)_
-
-## `csdx config:remove:rate-limit`
-
-Remove rate-limit of the organization
-
-```
-USAGE
-  $ csdx config:remove:rate-limit [--org <value>]
-
-FLAGS
-  --org=<value>  Provide the organization UID
-
-DESCRIPTION
-  Remove rate-limit of the organization
-
-EXAMPLES
-  $ csdx config:remove:rate-limit --org <<org_uid>>
-```
-
-_See code: [@contentstack/cli-config](https://github.com/contentstack/cli/blob/main/packages/contentstack-config/src/commands/config/remove/rate-limit.ts)_
-
-## `csdx config:set:base-branch`
-
-Set branch for CLI
-
-```
-USAGE
-  $ csdx config:set:base-branch [-k <value>] [--base-branch <value>]
-
-FLAGS
-  -k, --stack-api-key=<value>  Stack API key
-      --base-branch=<value>    Base branch (Target branch).
-
-DESCRIPTION
-  Set branch for CLI
-
-EXAMPLES
-  $ csdx config:set:base-branch
-
-  $ csdx config:set:base-branch --stack-api-key <value> --base-branch <value>
-```
-
-_See code: [@contentstack/cli-config](https://github.com/contentstack/cli/blob/main/packages/contentstack-config/src/commands/config/set/base-branch.ts)_
-
-## `csdx config:set:ea-header`
-
-Set Early Access header
-
-```
-USAGE
-  $ csdx config:set:ea-header [--header-alias <value>] [--header <value>]
-
-FLAGS
-  --header=<value>        (optional) Provide the Early Access header alias name.
-  --header-alias=<value>  (optional) Provide the Early Access header value.
-
-DESCRIPTION
-  Set Early Access header
-
-ALIASES
-  $ csdx config:set:ea-header
-
-EXAMPLES
-  $ csdx config:set:ea-header
-
-  $ csdx config:set:ea-header --header <value> --header-alias <value>
-```
-
-## `csdx config:set:early-access-header`
-
-Set Early Access header
-
-```
-USAGE
-  $ csdx config:set:early-access-header [--header-alias <value>] [--header <value>]
-
-FLAGS
-  --header=<value>        (optional) Provide the Early Access header alias name.
-  --header-alias=<value>  (optional) Provide the Early Access header value.
-
-DESCRIPTION
-  Set Early Access header
-
-ALIASES
-  $ csdx config:set:ea-header
-
-EXAMPLES
-  $ csdx config:set:early-access-header
-
-  $ csdx config:set:early-access-header --header <value> --header-alias <value>
-```
-
-_See code: [@contentstack/cli-config](https://github.com/contentstack/cli/blob/main/packages/contentstack-config/src/commands/config/set/early-access-header.ts)_
-
-## `csdx config:set:log`
-
-Set logging configuration for CLI
-
-```
-USAGE
-  $ csdx config:set:log [--level debug|info|warn|error] [--path <value>] [--show-console-logs]
-
-FLAGS
-  --level=<option>          Set the log level for the CLI. Defaults to "info" if not specified.
-                            <options: debug|info|warn|error>
-  --path=<value>            Specify the directory path where logs should be saved. Supports both relative and absolute
-                            paths. Defaults to ~/.contentstack/logs if not specified.
-  --[no-]show-console-logs  Enable console logging.
-
-DESCRIPTION
-  Set logging configuration for CLI
-
-EXAMPLES
-  $ csdx config:set:log
-
-  $ csdx config:set:log --level debug
-
-  $ csdx config:set:log --path ./logs
-
-  $ csdx config:set:log --level debug --path ./logs --show-console-logs
-
-  $ csdx config:set:log --no-show-console-logs
-
-  $ csdx config:set:log --level warn --show-console-logs
-
-  $ csdx config:set:log --path ~/custom/logs
-
-  $ csdx config:set:log --path /var/log/contentstack
-```
-
-_See code: [@contentstack/cli-config](https://github.com/contentstack/cli/blob/main/packages/contentstack-config/src/commands/config/set/log.ts)_
-
-## `csdx config:set:proxy`
-
-Set proxy configuration for CLI
-
-```
-USAGE
-  $ csdx config:set:proxy --host <value> --port <value> --protocol http|https [--username <value>]
-
-FLAGS
-  --host=<value>       (required) Proxy host address
-  --port=<value>       (required) Proxy port number
-  --protocol=<option>  (required) [default: http] Proxy protocol (http or https)
-                       <options: http|https>
-  --username=<value>   Proxy username (optional)
-
-DESCRIPTION
-  Set proxy configuration for CLI
-
-EXAMPLES
-  $ csdx config:set:proxy --host 127.0.0.1 --port 3128
-
-  $ csdx config:set:proxy --host proxy.example.com --port 8080 --protocol https
-
-  $ csdx config:set:proxy --host proxy.example.com --port 8080 --username user
-```
-
-_See code: [@contentstack/cli-config](https://github.com/contentstack/cli/blob/main/packages/contentstack-config/src/commands/config/set/proxy.ts)_
-
-## `csdx config:set:rate-limit`
-
-Set rate-limit for CLI
-
-```
-USAGE
-  $ csdx config:set:rate-limit [--org <value>] [--utilize <value>] [--limit-name <value>...] [--default]
-
-FLAGS
-  --default                Reset to default rate limit
-  --limit-name=<value>...  [Optional] Provide the limit names separated by commas ['limit', 'getLimit', 'bulkLimit']
-  --org=<value>            Provide the organization UID
-  --utilize=<value>        [default: 50] Provide the utilization percentages for rate limit, separated by commas
-
-DESCRIPTION
-  Set rate-limit for CLI
-
-EXAMPLES
-  $ csdx config:set:rate-limit --org <<org_uid>>
-
-  $ csdx config:set:rate-limit --org <<org_uid>> --utilize 70,80 --limit-name getLimit,limit
-
-  $ csdx config:set:rate-limit --org <<org_uid>> --default
-```
-
-_See code: [@contentstack/cli-config](https://github.com/contentstack/cli/blob/main/packages/contentstack-config/src/commands/config/set/rate-limit.ts)_
-
-## `csdx config:set:region [REGION]`
-
-Set region for CLI
-
-```
-USAGE
-  $ csdx config:set:region [REGION] [-d <value> -m <value> --ui-host <value> -n <value>] [--developer-hub <value>]
-    [--personalize <value>] [--launch <value>] [--studio <value>] [--auth-api <value>]
-
-ARGUMENTS
-  [REGION]  Name for the region
-
-FLAGS
-  -d, --cda=<value>            Custom host to set for content delivery API, if this flag is added then cma, ui-host and
-                               name flags are required
-  -m, --cma=<value>            Custom host to set for content management API, , if this flag is added then cda, ui-host
-                               and name flags are required
-  -n, --name=<value>           Name for the region, if this flag is added then cda, cma and ui-host flags are required
-      --auth-api=<value>       Custom host to set for Auth API
-      --developer-hub=<value>  Custom host to set for Developer hub API
-      --launch=<value>         Custom host to set for Launch API
-      --personalize=<value>    Custom host to set for Personalize API
-      --studio=<value>         Custom host to set for Studio API
-      --ui-host=<value>        Custom UI host to set for CLI, if this flag is added then cda, cma and name flags are
-                               required
-
-DESCRIPTION
-  Set region for CLI
-
-EXAMPLES
-  $ csdx config:set:region
-
-  $ csdx config:set:region AWS-NA
-
-  $ csdx config:set:region AWS-EU
-
-  $ csdx config:set:region AWS-AU
-
-  $ csdx config:set:region AZURE-NA
-
-  $ csdx config:set:region AZURE-EU
-
-  $ csdx config:set:region GCP-NA
-
-  $ csdx config:set:region GCP-EU
-
-  $ csdx config:set:region --cma <custom_cma_host_url> --cda <custom_cda_host_url> --ui-host <custom_ui_host_url> --name "India"
-
-  $ csdx config:set:region --cma <custom_cma_host_url> --cda <custom_cda_host_url> --ui-host <custom_ui_host_url> --name "India" --developer-hub <custom_developer_hub_url>
-
-  $ csdx config:set:region --cma <custom_cma_host_url> --cda <custom_cda_host_url> --ui-host <custom_ui_host_url> --name "India" --personalize <custom_personalize_url>
-
-  $ csdx config:set:region --cma <custom_cma_host_url> --cda <custom_cda_host_url> --ui-host <custom_ui_host_url> --name "India" --launch <custom_launch_url>
-
-  $ csdx config:set:region --cma <custom_cma_host_url> --cda <custom_cda_host_url> --ui-host <custom_ui_host_url> --name "India" --studio <custom_studio_url>
-
-  $ csdx config:set:region --cda <custom_cda_host_url> --cma <custom_cma_host_url> --ui-host <custom_ui_host_url> --name "India" --developer-hub <custom_developer_hub_url> --launch <custom_launch_url> --personalize <custom_personalize_url> --studio <custom_studio_url>
-```
-
-_See code: [@contentstack/cli-config](https://github.com/contentstack/cli/blob/main/packages/contentstack-config/src/commands/config/set/region.ts)_
-
-## `csdx help [COMMAND]`
-
-Display help for csdx.
-
-```
-USAGE
-  $ csdx help [COMMAND...] [-n]
-
-ARGUMENTS
-  [COMMAND...]  Command to show help for.
-
-FLAGS
-  -n, --nested-commands  Include all nested commands in the output.
-
-DESCRIPTION
-  Display help for csdx.
-```
-
-_See code: [@oclif/plugin-help](https://github.com/oclif/plugin-help/blob/6.2.44/src/commands/help.ts)_
-
-## `csdx launch`
-
-Launch related operations
-
-```
-USAGE
-  $ csdx launch [-d <value>] [-c <value>] [--type GitHub|FileUpload] [--framework Gatsby|NextJs|CRA (Create
-    React App)|CSR (Client-Side Rendered)|Analog|Angular|Nuxt|Astro|VueJs|Remix|Other] [--org <value>] [-n <value>] [-e
-    <value>] [--branch <value>] [--build-command <value>] [--out-dir <value>] [--server-command <value>]
-    [--variable-type Import variables from a stack|Manually add custom variables to the list|Import variables from the
-    .env.local file|Skip adding environment variables...] [-a <value>] [--env-variables <value>] [--redeploy-latest]
-    [--redeploy-last-upload] [--response-mode buffered|streaming]
-
-FLAGS
-  -a, --alias=<value>              [optional] Alias (name) for the delivery token.
-  -c, --config=<value>             Path to the local '.cs-launch.json' file
-  -d, --data-dir=<value>           Current working directory
-  -e, --environment=<value>        [optional] Environment name for the Launch project.
-  -n, --name=<value>               [optional] Name of the project.
-      --branch=<value>             [optional] GitHub branch name.
-      --build-command=<value>      [optional] Build Command.
-      --env-variables=<value>      [optional] Provide the environment variables in the key:value format, separated by
-                                   comma. For example: APP_ENV:prod, TEST_ENV:testVal.
-      --framework=<option>         [optional] Type of framework. <options: Gatsby|NextJS|Other>
-                                   <options: Gatsby|NextJs|CRA (Create React App)|CSR (Client-Side
-                                   Rendered)|Analog|Angular|Nuxt|Astro|VueJs|Remix|Other>
-      --org=<value>                [optional] Provide the organization UID to create a new project or deployment.
-      --out-dir=<value>            [optional] Output Directory.
-      --redeploy-last-upload       [optional] Redeploy with last file upload
-      --redeploy-latest            [optional] Redeploy latest commit/code
-      --response-mode=<option>     [optional] Provide mode for response. <options: buffered|streaming
-                                   <options: buffered|streaming>
-      --server-command=<value>     [optional] Server Command.
-      --type=<option>              [optional] Type of adapters. <options: GitHub|FileUpload>
-                                   <options: GitHub|FileUpload>
-      --variable-type=<option>...  [optional] Provide a variable type (can specify multiple times). <options: Import
-                                   variables from a stack|Manually add custom variables to the list|Import variables
-                                   from the .env.local file|Skip adding environment variables>
-                                   <options: Import variables from a stack|Manually add custom variables to the
-                                   list|Import variables from the .env.local file|Skip adding environment variables>
-
-DESCRIPTION
-  Launch related operations
-
-EXAMPLES
-  $ csdx launch
-
-  $ csdx launch --data-dir <path/of/current/working/dir>
-
-  $ csdx launch --config <path/to/launch/config/file>
-
-  $ csdx launch --type <options: GitHub|FileUpload>
-
-  $ csdx launch --data-dir <path/of/current/working/dir> --type <options: GitHub|FileUpload>
-
-  $ csdx launch --data-dir <path/of/current/working/dir> --redeploy-latest
-
-  $ csdx launch --data-dir <path/of/current/working/dir> --redeploy-last-upload
-
-  $ csdx launch --config <path/to/launch/config/file> --type <options: GitHub|FileUpload>
-
-  $ csdx launch --environment=<value> --redeploy-latest
-
-  $ csdx launch --config <path/to/launch/config/file> --type <options: GitHub|FileUpload> --name=<value> --environment=<value> --branch=<value> --build-command=<value> --framework=<option> --org=<value> --out-dir=<value>
-
-  $ csdx launch --config <path/to/launch/config/file> --type <options: GitHub|FileUpload> --name=<value> --environment=<value> --branch=<value> --build-command=<value> --framework=<option> --org=<value> --out-dir=<value> --server-command=<value>
-
-  $ csdx launch --config <path/to/launch/config/file> --type <options: GitHub|FileUpload> --name=<value> --environment=<value> --branch=<value> --build-command=<value> --framework=<option> --org=<value> --out-dir=<value> --server-command=<value> --response-mode=streaming
-
-  $ csdx launch --config <path/to/launch/config/file> --type <options: GitHub|FileUpload> --name=<value> --environment=<value> --branch=<value> --build-command=<value> --framework=<option> --org=<value> --out-dir=<value> --variable-type="Import variables from a stack" --alias=<value>
-
-  $ csdx launch --config <path/to/launch/config/file> --type <options: GitHub|FileUpload> --name=<value> --environment=<value> --branch=<value> --build-command=<value> --framework=<option> --org=<value> --out-dir=<value> --variable-type="Manually add custom variables to the list" --env-variables="APP_ENV:prod, TEST_ENV:testVal"
-
-  $ csdx launch --config <path/to/launch/config/file> --type <options: GitHub|FileUpload> --name=<value> --environment=<value> --branch=<value> --build-command=<value> --framework=<option> --org=<value> --out-dir=<value> --variable-type="Import variables from a stack" --variable-type="Manually add custom variables to the list" --alias=<value>
-```
-
-_See code: [@contentstack/cli-launch](https://github.com/contentstack/launch-cli/blob/main/packages/contentstack-launch/src/commands/launch/index.ts)_
-
-## `csdx launch:deployments`
-
-Show list of deployments for an environment
-
-```
-USAGE
-  $ csdx launch:deployments [-d <value>] [-c <value>] [--org <value>] [--project <value>] [-e <value>]
-
-FLAGS
-  -c, --config=<value>       Path to the local '.cs-launch.json' file
-  -d, --data-dir=<value>     Current working directory
-  -e, --environment=<value>  Environment name or UID
-      --org=<value>          [Optional] Provide the organization UID
-      --project=<value>      [Optional] Provide the project UID
-
-DESCRIPTION
-  Show list of deployments for an environment
-
-EXAMPLES
-  $ csdx launch:deployments
-
-  $ csdx launch:deployments -d "current working directory"
-
-  $ csdx launch:deployments -c "path to the local config file"
-
-  $ csdx launch:deployments -e "environment number or uid" --org=<org UID> --project=<Project UID>
-```
-
-_See code: [@contentstack/cli-launch](https://github.com/contentstack/launch-cli/blob/main/packages/contentstack-launch/src/commands/launch/deployments.ts)_
-
-## `csdx launch:environments`
-
-Show list of environments for a project
-
-```
-USAGE
-  $ csdx launch:environments [-d <value>] [-c <value>] [--org <value>] [--project <value>]
-
-FLAGS
-  -c, --config=<value>    Path to the local '.cs-launch.json' file
-  -d, --data-dir=<value>  Current working directory
-      --org=<value>       [Optional] Provide the organization UID
-      --project=<value>   [Optional] Provide the project UID
-
-DESCRIPTION
-  Show list of environments for a project
-
-EXAMPLES
-  $ csdx launch:environments
-
-  $ csdx launch:environments -d "current working directory"
-
-  $ csdx launch:environments -c "path to the local config file"
-
-  $ csdx launch:environments --org=<org UID> --project=<Project UID>
-```
-
-_See code: [@contentstack/cli-launch](https://github.com/contentstack/launch-cli/blob/main/packages/contentstack-launch/src/commands/launch/environments.ts)_
-
-## `csdx launch:functions`
-
-Serve cloud functions
-
-```
-USAGE
-  $ csdx launch:functions [-p <value>] [-d <value>]
-
-FLAGS
-  -d, --data-dir=<value>  Current working directory
-  -p, --port=<value>      [default: 3000] Port number
-
-DESCRIPTION
-  Serve cloud functions
-
-EXAMPLES
-  $ csdx launch:functions
-
-  $ csdx launch:functions --port=port
-
-  $ csdx launch:functions --data-dir <path/of/current/working/dir>
-
-  $ csdx launch:functions --data-dir <path/of/current/working/dir> -p "port number"
-```
-
-_See code: [@contentstack/cli-launch](https://github.com/contentstack/launch-cli/blob/main/packages/contentstack-launch/src/commands/launch/functions.ts)_
-
-## `csdx launch:logs`
-
-Show deployment or server logs
-
-```
-USAGE
-  $ csdx launch:logs [-d <value>] [-c <value>] [-e <value>] [--deployment <value>] [--type d|s] [--org <value>]
-    [--project <value>]
-
-FLAGS
-  -c, --config=<value>       Path to the local '.cs-launch.json' file
-  -d, --data-dir=<value>     Current working directory
-  -e, --environment=<value>  Environment name or UID
-      --deployment=<value>   Deployment number or UID
-      --org=<value>          [Optional] Provide the organization UID
-      --project=<value>      [Optional] Provide the project UID
-      --type=<option>        [default: s] Type of flags to show logs. By default, these are server logs. Options [d -
-                             deployment logs, s - server logs]
-                             <options: d|s>
-
-DESCRIPTION
-  Show deployment or server logs
-
-EXAMPLES
-  $ csdx launch:logs
-
-  $ csdx launch:logs --data-dir <path/of/current/working/dir>
-
-  $ csdx launch:logs --data-dir <path/of/current/working/dir> --type <options: d|s>
-
-  $ csdx launch:logs --config <path/to/launch/config/file> --type <options: d|s>
-
-  $ csdx launch:logs --deployment=deployment
-
-  $ csdx launch:logs --environment=environment
-
-  $ csdx launch:logs --environment=environment --deployment=deployment
-
-  $ csdx launch:logs --environment=environment --type <options: d|s>
-
-  $ csdx launch:logs --environment=environment --data-dir <path/of/current/working/dir> --deployment=deployment
-
-  $ csdx launch:logs --environment=environment --config <path/to/launch/config/file> --deployment=deployment
-```
-
-_See code: [@contentstack/cli-launch](https://github.com/contentstack/launch-cli/blob/main/packages/contentstack-launch/src/commands/launch/logs.ts)_
-
-## `csdx launch:open`
-
-Open a website for an environment
-
-```
-USAGE
-  $ csdx launch:open [-d <value>] [-c <value>] [--org <value>] [--project <value>] [-e <value>]
-
-FLAGS
-  -c, --config=<value>       Path to the local '.cs-launch.json' file
-  -d, --data-dir=<value>     Current working directory
-  -e, --environment=<value>  Environment name or UID
-      --org=<value>          [Optional] Provide the organization UID
-      --project=<value>      [Optional] Provide the project UID
-
-DESCRIPTION
-  Open a website for an environment
-
-EXAMPLES
-  $ csdx launch:open
-
-  $ csdx launch:open --config <path/to/launch/config/file>
-
-  $ csdx launch:open --data-dir <path/of/current/working/dir>
-
-  $ csdx launch:open --environment=environment
-
-  $ csdx launch:open --environment=environment --config <path/to/launch/config/file>
-
-  $ csdx launch:open --environment=environment --data-dir <path/of/current/working/dir>
-```
-
-_See code: [@contentstack/cli-launch](https://github.com/contentstack/launch-cli/blob/main/packages/contentstack-launch/src/commands/launch/open.ts)_
-
-## `csdx launch:rollback`
-
-Roll back to previous deployment
-
-```
-USAGE
-  $ csdx launch:rollback [-d <value>] [-c <value>] [--org <value>] [--project <value>] [-e <value>] [--deployment
-    <value>] [--reason <value>]
-
-FLAGS
-  -c, --config=<value>       Path to the local '.cs-launch.json' file
-  -d, --data-dir=<value>     Current working directory
-  -e, --environment=<value>  Environment name or UID
-      --deployment=<value>   [Optional] Deployment UID to roll back to
-      --org=<value>          [Optional] Provide the organization UID
-      --project=<value>      [Optional] Provide the project UID
-      --reason=<value>       [Optional] Reason for the rollback (saved to audit log)
-
-DESCRIPTION
-  Roll back to previous deployment
-
-EXAMPLES
-  $ csdx launch:rollback
-
-  $ csdx launch:rollback -d "current working directory"
-
-  $ csdx launch:rollback -c "path to the local config file"
-
-  $ csdx launch:rollback -e "environment number or uid" --deployment=<deployment UID> --org=<org UID> --project=<Project UID> --reason="restoring previous build"
-```
-
-_See code: [@contentstack/cli-launch](https://github.com/contentstack/launch-cli/blob/main/packages/contentstack-launch/src/commands/launch/rollback.ts)_
-
-## `csdx login`
-
-User sessions login
-
-```
-USAGE
-  $ csdx login [-u <value> | --oauth] [-p <value> | ]
-
-FLAGS
-  -p, --password=<value>  Password of your Contentstack app.
-  -u, --username=<value>  Email address of your Contentstack account.
-      --oauth             Enables single sign-on (SSO) in Contentstack CLI.
-
-DESCRIPTION
-  User sessions login
-
-ALIASES
-  $ csdx login
-
-EXAMPLES
-  $ csdx auth:login
-
-  $ csdx auth:login -u <username>
-
-  $ csdx auth:login -u <username> -p <password>
-
-  $ csdx auth:login --username <username>
-
-  $ csdx auth:login --username <username> --password <password>
-```
-
-## `csdx logout`
-
-User session logout
+## Installation
 
+```sh
+npm install -g @contentstack/cli
 ```
-USAGE
-  $ csdx logout [-y]
 
-FLAGS
-  -y, --yes  Force log out by skipping the confirmation.
+## Usage
 
-DESCRIPTION
-  User session logout
-
-ALIASES
-  $ csdx logout
-
-EXAMPLES
-  $ csdx auth:logout
-
-  $ csdx auth:logout -y
-
-  $ csdx auth:logout --yes
-```
-
-## `csdx plugins`
-
-List installed plugins.
-
-```
-USAGE
-  $ csdx plugins [--json] [--core]
-
-FLAGS
-  --core  Show core plugins.
-
-GLOBAL FLAGS
-  --json  Format output as json.
-
-DESCRIPTION
-  List installed plugins.
-
-EXAMPLES
-  $ csdx plugins
-```
-
-_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/v5.4.56/src/commands/plugins/index.ts)_
-
-## `csdx plugins:add PLUGIN`
-
-Installs a plugin into csdx.
-
-```
-USAGE
-  $ csdx plugins:add PLUGIN... [--json] [-f] [-h] [-s | -v]
-
-ARGUMENTS
-  PLUGIN...  Plugin to install.
-
-FLAGS
-  -f, --force    Force npm to fetch remote resources even if a local copy exists on disk.
-  -h, --help     Show CLI help.
-  -s, --silent   Silences npm output.
-  -v, --verbose  Show verbose npm output.
-
-GLOBAL FLAGS
-  --json  Format output as json.
-
-DESCRIPTION
-  Installs a plugin into csdx.
-
-  Uses npm to install plugins.
-
-  Installation of a user-installed plugin will override a core plugin.
-
-  Use the CSDX_NPM_LOG_LEVEL environment variable to set the npm loglevel.
-  Use the CSDX_NPM_REGISTRY environment variable to set the npm registry.
-
-ALIASES
-  $ csdx plugins:add
-
-EXAMPLES
-  Install a plugin from npm registry.
-
-    $ csdx plugins:add myplugin
-
-  Install a plugin from a github url.
-
-    $ csdx plugins:add https://github.com/someuser/someplugin
-
-  Install a plugin from a github slug.
-
-    $ csdx plugins:add someuser/someplugin
-```
-
-## `csdx plugins:inspect PLUGIN...`
-
-Displays installation properties of a plugin.
-
-```
-USAGE
-  $ csdx plugins:inspect PLUGIN...
-
-ARGUMENTS
-  PLUGIN...  [default: .] Plugin to inspect.
-
-FLAGS
-  -h, --help     Show CLI help.
-  -v, --verbose
-
-GLOBAL FLAGS
-  --json  Format output as json.
-
-DESCRIPTION
-  Displays installation properties of a plugin.
-
-EXAMPLES
-  $ csdx plugins:inspect myplugin
-```
-
-_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/v5.4.56/src/commands/plugins/inspect.ts)_
-
-## `csdx plugins:install PLUGIN`
-
-Installs a plugin into csdx.
-
-```
-USAGE
-  $ csdx plugins:install PLUGIN... [--json] [-f] [-h] [-s | -v]
-
-ARGUMENTS
-  PLUGIN...  Plugin to install.
-
-FLAGS
-  -f, --force    Force npm to fetch remote resources even if a local copy exists on disk.
-  -h, --help     Show CLI help.
-  -s, --silent   Silences npm output.
-  -v, --verbose  Show verbose npm output.
-
-GLOBAL FLAGS
-  --json  Format output as json.
-
-DESCRIPTION
-  Installs a plugin into csdx.
-
-  Uses npm to install plugins.
-
-  Installation of a user-installed plugin will override a core plugin.
-
-  Use the CSDX_NPM_LOG_LEVEL environment variable to set the npm loglevel.
-  Use the CSDX_NPM_REGISTRY environment variable to set the npm registry.
-
-ALIASES
-  $ csdx plugins:add
-
-EXAMPLES
-  Install a plugin from npm registry.
-
-    $ csdx plugins:install myplugin
-
-  Install a plugin from a github url.
-
-    $ csdx plugins:install https://github.com/someuser/someplugin
-
-  Install a plugin from a github slug.
-
-    $ csdx plugins:install someuser/someplugin
-```
-
-_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/v5.4.56/src/commands/plugins/install.ts)_
-
-## `csdx plugins:link PATH`
-
-Links a plugin into the CLI for development.
-
-```
-USAGE
-  $ csdx plugins:link PATH [-h] [--install] [-v]
-
-ARGUMENTS
-  PATH  [default: .] path to plugin
-
-FLAGS
-  -h, --help          Show CLI help.
-  -v, --verbose
-      --[no-]install  Install dependencies after linking the plugin.
-
-DESCRIPTION
-  Links a plugin into the CLI for development.
-
-  Installation of a linked plugin will override a user-installed or core plugin.
-
-  e.g. If you have a user-installed or core plugin that has a 'hello' command, installing a linked plugin with a 'hello'
-  command will override the user-installed or core plugin implementation. This is useful for development work.
-
-
-EXAMPLES
-  $ csdx plugins:link myplugin
-```
-
-_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/v5.4.56/src/commands/plugins/link.ts)_
-
-## `csdx plugins:remove [PLUGIN]`
-
-Removes a plugin from the CLI.
-
-```
-USAGE
-  $ csdx plugins:remove [PLUGIN...] [-h] [-v]
-
-ARGUMENTS
-  [PLUGIN...]  plugin to uninstall
-
-FLAGS
-  -h, --help     Show CLI help.
-  -v, --verbose
-
-DESCRIPTION
-  Removes a plugin from the CLI.
-
-ALIASES
-  $ csdx plugins:unlink
-  $ csdx plugins:remove
-
-EXAMPLES
-  $ csdx plugins:remove myplugin
-```
-
-## `csdx plugins:reset`
-
-Remove all user-installed and linked plugins.
-
-```
-USAGE
-  $ csdx plugins:reset [--hard] [--reinstall]
-
-FLAGS
-  --hard       Delete node_modules and package manager related files in addition to uninstalling plugins.
-  --reinstall  Reinstall all plugins after uninstalling.
-```
-
-_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/v5.4.56/src/commands/plugins/reset.ts)_
-
-## `csdx plugins:uninstall [PLUGIN]`
-
-Removes a plugin from the CLI.
-
-```
-USAGE
-  $ csdx plugins:uninstall [PLUGIN...] [-h] [-v]
-
-ARGUMENTS
-  [PLUGIN...]  plugin to uninstall
-
-FLAGS
-  -h, --help     Show CLI help.
-  -v, --verbose
-
-DESCRIPTION
-  Removes a plugin from the CLI.
-
-ALIASES
-  $ csdx plugins:unlink
-  $ csdx plugins:remove
-
-EXAMPLES
-  $ csdx plugins:uninstall myplugin
-```
-
-_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/v5.4.56/src/commands/plugins/uninstall.ts)_
-
-## `csdx plugins:unlink [PLUGIN]`
-
-Removes a plugin from the CLI.
-
-```
-USAGE
-  $ csdx plugins:unlink [PLUGIN...] [-h] [-v]
-
-ARGUMENTS
-  [PLUGIN...]  plugin to uninstall
-
-FLAGS
-  -h, --help     Show CLI help.
-  -v, --verbose
-
-DESCRIPTION
-  Removes a plugin from the CLI.
-
-ALIASES
-  $ csdx plugins:unlink
-  $ csdx plugins:remove
-
-EXAMPLES
-  $ csdx plugins:unlink myplugin
-```
-
-## `csdx plugins:update`
-
-Update installed plugins.
-
-```
-USAGE
-  $ csdx plugins:update [-h] [-v]
-
-FLAGS
-  -h, --help     Show CLI help.
-  -v, --verbose
-
-DESCRIPTION
-  Update installed plugins.
+```sh
+csdx --version
+csdx --help
+csdx auth:login
 ```
 
-_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/v5.4.56/src/commands/plugins/update.ts)_
+For complete documentation, visit the [Contentstack CLI docs](https://www.contentstack.com/docs/developers/cli).
 
-## `csdx tokens`
+## Bundled Plugins
 
-Lists all existing tokens added to the session
-
-```
-USAGE
-  $ csdx tokens [--columns <value>] [--sort <value>] [--filter <value>] [--csv] [--no-truncate]
-    [--no-header] [--output csv|json|yaml]
+| Plugin | Description |
+|--------|-------------|
+| [`@contentstack/cli-auth`](https://www.npmjs.com/package/@contentstack/cli-auth) | Authentication — login, logout, token management |
+| [`@contentstack/cli-config`](https://www.npmjs.com/package/@contentstack/cli-config) | Region and early-access header configuration |
+| [`@contentstack/cli-cm-import`](https://www.npmjs.com/package/@contentstack/cli-cm-import) | Import stacks and modules into Contentstack |
+| [`@contentstack/cli-cm-export`](https://www.npmjs.com/package/@contentstack/cli-cm-export) | Export stacks and modules from Contentstack |
+| [`@contentstack/cli-cm-seed`](https://www.npmjs.com/package/@contentstack/cli-cm-seed) | Seed a stack from a GitHub repository |
+| [`@contentstack/cli-cm-bootstrap`](https://www.npmjs.com/package/@contentstack/cli-cm-bootstrap) | Bootstrap a new Contentstack project |
+| [`@contentstack/cli-cm-export-to-csv`](https://www.npmjs.com/package/@contentstack/cli-cm-export-to-csv) | Export entries, taxonomies, terms, and org users to CSV |
+| [`@contentstack/cli-cm-clone`](https://www.npmjs.com/package/@contentstack/cli-cm-clone) | Clone a stack to another stack |
+| [`@contentstack/cli-cm-migrate-rte`](https://www.npmjs.com/package/@contentstack/cli-cm-migrate-rte) | Migrate HTML RTE entries to JSON RTE |
+| [`@contentstack/cli-migration`](https://www.npmjs.com/package/@contentstack/cli-migration) | Run stack migration scripts |
+| [`@contentstack/cli-cm-bulk-publish`](https://www.npmjs.com/package/@contentstack/cli-cm-bulk-publish) | Bulk publish and unpublish entries and assets |
+| [`@contentstack/cli-cm-branches`](https://www.npmjs.com/package/@contentstack/cli-cm-branches) | Branch management — create, diff, and merge |
+| [`@contentstack/cli-audit`](https://www.npmjs.com/package/@contentstack/cli-audit) | Audit and fix content type and entry issues |
+| [`@contentstack/cli-launch`](https://www.npmjs.com/package/@contentstack/cli-launch) | Deploy and manage Contentstack Launch projects |
 
-TABLE FLAGS
-  --columns=<value>  Specify columns to display, comma-separated.
-  --csv              Output results in CSV format.
-  --filter=<value>   Filter rows by a column value (e.g., name=foo).
-  --no-header        Hide table headers in output.
-  --no-truncate      Prevent truncation of long text in columns.
-  --output=<option>  Specify output format: csv, json, or yaml.
-                     <options: csv|json|yaml>
-  --sort=<value>     Sort the table by a column. Use "-" for descending.
+> For new bulk workflows, prefer [`@contentstack/cli-bulk-operations`](https://www.npmjs.com/package/@contentstack/cli-bulk-operations) — it replaces `cli-cm-bulk-publish` with optimized, dedicated commands.
 
-DESCRIPTION
-  Lists all existing tokens added to the session
+## Installable Plugins
 
-ALIASES
-  $ csdx tokens
+These are Contentstack-owned plugins not bundled in the default install. Add any of them with:
 
-EXAMPLES
-  $ csdx auth:tokens
+```sh
+csdx plugins:install <plugin-name>
 ```
 
-## `csdx whoami`
+| Plugin | Description |
+|--------|-------------|
+| [`@contentstack/apps-cli`](https://www.npmjs.com/package/@contentstack/apps-cli) | Build, deploy, and manage Contentstack apps |
+| [`contentstack-cli-tsgen`](https://www.npmjs.com/package/contentstack-cli-tsgen) `*` | Generate TypeScript typings from a stack's content types |
+| [`contentstack-cli-content-type`](https://www.npmjs.com/package/contentstack-cli-content-type) `*` | Retrieve and inspect content types in a stack |
+| [`@contentstack/cli-bulk-operations`](https://www.npmjs.com/package/@contentstack/cli-bulk-operations) | Run bulk operations across stack content |
+| [`@contentstack/cli-cm-regex-validate`](https://www.npmjs.com/package/@contentstack/cli-cm-regex-validate) | Validate regex properties on content type and global fields |
+| [`@contentstack/cli-external-migrate`](https://www.npmjs.com/package/@contentstack/cli-external-migrate) | Migrate content from an external source into Contentstack |
+| [`@contentstack/cli-cm-export-query`](https://www.npmjs.com/package/@contentstack/cli-cm-export-query) | Export stack content using query filters |
 
-Display current users email address
+`*` Published before the `@contentstack/` npm scope was adopted — the package name is correct.
 
-```
-USAGE
-  $ csdx whoami
-
-DESCRIPTION
-  Display current users email address
+## License
 
-ALIASES
-  $ csdx whoami
-
-EXAMPLES
-  $ csdx auth:whoami
-```
-<!-- commandsstop -->
+[MIT](https://github.com/contentstack/cli/blob/main/LICENSE)

From 779ede379c1725b5fd394384ada3830e7e5f663d Mon Sep 17 00:00:00 2001
From: raj pandey <raj.pandey@contentstack.com>
Date: Wed, 5 Aug 2026 17:45:44 +0530
Subject: [PATCH 2/4] docs(cli): remove bulk-operations, asterisk footnotes,
 and bulk note

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---
 packages/contentstack/README.md | 9 ++-------
 1 file changed, 2 insertions(+), 7 deletions(-)

diff --git a/packages/contentstack/README.md b/packages/contentstack/README.md
index 520ad1ee1b..811d4d722d 100644
--- a/packages/contentstack/README.md
+++ b/packages/contentstack/README.md
@@ -44,8 +44,6 @@ For complete documentation, visit the [Contentstack CLI docs](https://www.conten
 | [`@contentstack/cli-audit`](https://www.npmjs.com/package/@contentstack/cli-audit) | Audit and fix content type and entry issues |
 | [`@contentstack/cli-launch`](https://www.npmjs.com/package/@contentstack/cli-launch) | Deploy and manage Contentstack Launch projects |
 
-> For new bulk workflows, prefer [`@contentstack/cli-bulk-operations`](https://www.npmjs.com/package/@contentstack/cli-bulk-operations) — it replaces `cli-cm-bulk-publish` with optimized, dedicated commands.
-
 ## Installable Plugins
 
 These are Contentstack-owned plugins not bundled in the default install. Add any of them with:
@@ -57,15 +55,12 @@ csdx plugins:install <plugin-name>
 | Plugin | Description |
 |--------|-------------|
 | [`@contentstack/apps-cli`](https://www.npmjs.com/package/@contentstack/apps-cli) | Build, deploy, and manage Contentstack apps |
-| [`contentstack-cli-tsgen`](https://www.npmjs.com/package/contentstack-cli-tsgen) `*` | Generate TypeScript typings from a stack's content types |
-| [`contentstack-cli-content-type`](https://www.npmjs.com/package/contentstack-cli-content-type) `*` | Retrieve and inspect content types in a stack |
-| [`@contentstack/cli-bulk-operations`](https://www.npmjs.com/package/@contentstack/cli-bulk-operations) | Run bulk operations across stack content |
+| [`contentstack-cli-tsgen`](https://www.npmjs.com/package/contentstack-cli-tsgen) | Generate TypeScript typings from a stack's content types |
+| [`contentstack-cli-content-type`](https://www.npmjs.com/package/contentstack-cli-content-type) | Retrieve and inspect content types in a stack |
 | [`@contentstack/cli-cm-regex-validate`](https://www.npmjs.com/package/@contentstack/cli-cm-regex-validate) | Validate regex properties on content type and global fields |
 | [`@contentstack/cli-external-migrate`](https://www.npmjs.com/package/@contentstack/cli-external-migrate) | Migrate content from an external source into Contentstack |
 | [`@contentstack/cli-cm-export-query`](https://www.npmjs.com/package/@contentstack/cli-cm-export-query) | Export stack content using query filters |
 
-`*` Published before the `@contentstack/` npm scope was adopted — the package name is correct.
-
 ## License
 
 [MIT](https://github.com/contentstack/cli/blob/main/LICENSE)

From 53dbeaad0b4e2a15c8d548e487ad4653606851d8 Mon Sep 17 00:00:00 2001
From: raj pandey <raj.pandey@contentstack.com>
Date: Wed, 5 Aug 2026 18:04:12 +0530
Subject: [PATCH 3/4] docs(cli): add documentation links to plugin tables (v1)

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---
 packages/contentstack/README.md | 48 ++++++++++++++++-----------------
 1 file changed, 24 insertions(+), 24 deletions(-)

diff --git a/packages/contentstack/README.md b/packages/contentstack/README.md
index 811d4d722d..e963823567 100644
--- a/packages/contentstack/README.md
+++ b/packages/contentstack/README.md
@@ -27,22 +27,22 @@ For complete documentation, visit the [Contentstack CLI docs](https://www.conten
 
 ## Bundled Plugins
 
-| Plugin | Description |
-|--------|-------------|
-| [`@contentstack/cli-auth`](https://www.npmjs.com/package/@contentstack/cli-auth) | Authentication — login, logout, token management |
-| [`@contentstack/cli-config`](https://www.npmjs.com/package/@contentstack/cli-config) | Region and early-access header configuration |
-| [`@contentstack/cli-cm-import`](https://www.npmjs.com/package/@contentstack/cli-cm-import) | Import stacks and modules into Contentstack |
-| [`@contentstack/cli-cm-export`](https://www.npmjs.com/package/@contentstack/cli-cm-export) | Export stacks and modules from Contentstack |
-| [`@contentstack/cli-cm-seed`](https://www.npmjs.com/package/@contentstack/cli-cm-seed) | Seed a stack from a GitHub repository |
-| [`@contentstack/cli-cm-bootstrap`](https://www.npmjs.com/package/@contentstack/cli-cm-bootstrap) | Bootstrap a new Contentstack project |
-| [`@contentstack/cli-cm-export-to-csv`](https://www.npmjs.com/package/@contentstack/cli-cm-export-to-csv) | Export entries, taxonomies, terms, and org users to CSV |
-| [`@contentstack/cli-cm-clone`](https://www.npmjs.com/package/@contentstack/cli-cm-clone) | Clone a stack to another stack |
-| [`@contentstack/cli-cm-migrate-rte`](https://www.npmjs.com/package/@contentstack/cli-cm-migrate-rte) | Migrate HTML RTE entries to JSON RTE |
-| [`@contentstack/cli-migration`](https://www.npmjs.com/package/@contentstack/cli-migration) | Run stack migration scripts |
-| [`@contentstack/cli-cm-bulk-publish`](https://www.npmjs.com/package/@contentstack/cli-cm-bulk-publish) | Bulk publish and unpublish entries and assets |
-| [`@contentstack/cli-cm-branches`](https://www.npmjs.com/package/@contentstack/cli-cm-branches) | Branch management — create, diff, and merge |
-| [`@contentstack/cli-audit`](https://www.npmjs.com/package/@contentstack/cli-audit) | Audit and fix content type and entry issues |
-| [`@contentstack/cli-launch`](https://www.npmjs.com/package/@contentstack/cli-launch) | Deploy and manage Contentstack Launch projects |
+| Plugin | Description | Docs |
+|--------|-------------|------|
+| [`@contentstack/cli-auth`](https://www.npmjs.com/package/@contentstack/cli-auth) | Authentication — login, logout, token management | [Docs](https://www.contentstack.com/docs/headless-cms/cli-authentication) |
+| [`@contentstack/cli-config`](https://www.npmjs.com/package/@contentstack/cli-config) | Region and early-access header configuration | [Docs](https://www.contentstack.com/docs/headless-cms/configure-regions-in-the-cli) |
+| [`@contentstack/cli-cm-import`](https://www.npmjs.com/package/@contentstack/cli-cm-import) | Import stacks and modules into Contentstack | [Docs](https://www.contentstack.com/docs/headless-cms/import-content-using-the-cli) |
+| [`@contentstack/cli-cm-export`](https://www.npmjs.com/package/@contentstack/cli-cm-export) | Export stacks and modules from Contentstack | [Docs](https://www.contentstack.com/docs/headless-cms/export-content-using-the-cli) |
+| [`@contentstack/cli-cm-seed`](https://www.npmjs.com/package/@contentstack/cli-cm-seed) | Seed a stack from a GitHub repository | [Docs](https://www.contentstack.com/docs/headless-cms/import-content-using-the-seed-command) |
+| [`@contentstack/cli-cm-bootstrap`](https://www.npmjs.com/package/@contentstack/cli-cm-bootstrap) | Bootstrap a new Contentstack project | — |
+| [`@contentstack/cli-cm-export-to-csv`](https://www.npmjs.com/package/@contentstack/cli-cm-export-to-csv) | Export entries, taxonomies, terms, and org users to CSV | [Docs](https://www.contentstack.com/docs/headless-cms/export-content-to-csv-file/) |
+| [`@contentstack/cli-cm-clone`](https://www.npmjs.com/package/@contentstack/cli-cm-clone) | Clone a stack to another stack | [Docs](https://www.contentstack.com/docs/headless-cms/cloning-a-stack) |
+| [`@contentstack/cli-cm-migrate-rte`](https://www.npmjs.com/package/@contentstack/cli-cm-migrate-rte) | Migrate HTML RTE entries to JSON RTE | [Docs](https://www.contentstack.com/docs/headless-cms/migrate-content-from-html-rte-to-json-rte) |
+| [`@contentstack/cli-migration`](https://www.npmjs.com/package/@contentstack/cli-migration) | Run stack migration scripts | [Docs](https://www.contentstack.com/docs/headless-cms/migrate-your-content-using-the-cli-migration-command/) |
+| [`@contentstack/cli-cm-bulk-publish`](https://www.npmjs.com/package/@contentstack/cli-cm-bulk-publish) | Bulk publish and unpublish entries and assets | [Docs](https://www.contentstack.com/docs/headless-cms/bulk-publish-and-unpublish-content) |
+| [`@contentstack/cli-cm-branches`](https://www.npmjs.com/package/@contentstack/cli-cm-branches) | Branch management — create, diff, and merge | [Docs](https://www.contentstack.com/docs/headless-cms/compare-and-merge-branches-using-the-cli/) |
+| [`@contentstack/cli-audit`](https://www.npmjs.com/package/@contentstack/cli-audit) | Audit and fix content type and entry issues | [Docs](https://www.contentstack.com/docs/headless-cms/audit-plugin) |
+| [`@contentstack/cli-launch`](https://www.npmjs.com/package/@contentstack/cli-launch) | Deploy and manage Contentstack Launch projects | [Docs](https://www.contentstack.com/docs/headless-cms/cli-for-launch/) |
 
 ## Installable Plugins
 
@@ -52,14 +52,14 @@ These are Contentstack-owned plugins not bundled in the default install. Add any
 csdx plugins:install <plugin-name>
 ```
 
-| Plugin | Description |
-|--------|-------------|
-| [`@contentstack/apps-cli`](https://www.npmjs.com/package/@contentstack/apps-cli) | Build, deploy, and manage Contentstack apps |
-| [`contentstack-cli-tsgen`](https://www.npmjs.com/package/contentstack-cli-tsgen) | Generate TypeScript typings from a stack's content types |
-| [`contentstack-cli-content-type`](https://www.npmjs.com/package/contentstack-cli-content-type) | Retrieve and inspect content types in a stack |
-| [`@contentstack/cli-cm-regex-validate`](https://www.npmjs.com/package/@contentstack/cli-cm-regex-validate) | Validate regex properties on content type and global fields |
-| [`@contentstack/cli-external-migrate`](https://www.npmjs.com/package/@contentstack/cli-external-migrate) | Migrate content from an external source into Contentstack |
-| [`@contentstack/cli-cm-export-query`](https://www.npmjs.com/package/@contentstack/cli-cm-export-query) | Export stack content using query filters |
+| Plugin | Description | Docs |
+|--------|-------------|------|
+| [`@contentstack/apps-cli`](https://www.npmjs.com/package/@contentstack/apps-cli) | Build, deploy, and manage Contentstack apps | — |
+| [`contentstack-cli-tsgen`](https://www.npmjs.com/package/contentstack-cli-tsgen) | Generate TypeScript typings from a stack's content types | — |
+| [`contentstack-cli-content-type`](https://www.npmjs.com/package/contentstack-cli-content-type) | Retrieve and inspect content types in a stack | — |
+| [`@contentstack/cli-cm-regex-validate`](https://www.npmjs.com/package/@contentstack/cli-cm-regex-validate) | Validate regex properties on content type and global fields | — |
+| [`@contentstack/cli-external-migrate`](https://www.npmjs.com/package/@contentstack/cli-external-migrate) | Migrate content from an external source into Contentstack | — |
+| [`@contentstack/cli-cm-export-query`](https://www.npmjs.com/package/@contentstack/cli-cm-export-query) | Export stack content using query filters | — |
 
 ## License
 

From f64e250d64741f314a8ddf933b28032ac3ded602 Mon Sep 17 00:00:00 2001
From: raj pandey <raj.pandey@contentstack.com>
Date: Wed, 5 Aug 2026 18:11:17 +0530
Subject: [PATCH 4/4] docs(cli): add all verified documentation links to plugin
 tables (v1)

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---
 packages/contentstack/README.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/packages/contentstack/README.md b/packages/contentstack/README.md
index e963823567..972be03913 100644
--- a/packages/contentstack/README.md
+++ b/packages/contentstack/README.md
@@ -34,7 +34,7 @@ For complete documentation, visit the [Contentstack CLI docs](https://www.conten
 | [`@contentstack/cli-cm-import`](https://www.npmjs.com/package/@contentstack/cli-cm-import) | Import stacks and modules into Contentstack | [Docs](https://www.contentstack.com/docs/headless-cms/import-content-using-the-cli) |
 | [`@contentstack/cli-cm-export`](https://www.npmjs.com/package/@contentstack/cli-cm-export) | Export stacks and modules from Contentstack | [Docs](https://www.contentstack.com/docs/headless-cms/export-content-using-the-cli) |
 | [`@contentstack/cli-cm-seed`](https://www.npmjs.com/package/@contentstack/cli-cm-seed) | Seed a stack from a GitHub repository | [Docs](https://www.contentstack.com/docs/headless-cms/import-content-using-the-seed-command) |
-| [`@contentstack/cli-cm-bootstrap`](https://www.npmjs.com/package/@contentstack/cli-cm-bootstrap) | Bootstrap a new Contentstack project | — |
+| [`@contentstack/cli-cm-bootstrap`](https://www.npmjs.com/package/@contentstack/cli-cm-bootstrap) | Bootstrap a new Contentstack project | [Docs](https://www.contentstack.com/docs/headless-cms/bootstrap-starter-apps/) |
 | [`@contentstack/cli-cm-export-to-csv`](https://www.npmjs.com/package/@contentstack/cli-cm-export-to-csv) | Export entries, taxonomies, terms, and org users to CSV | [Docs](https://www.contentstack.com/docs/headless-cms/export-content-to-csv-file/) |
 | [`@contentstack/cli-cm-clone`](https://www.npmjs.com/package/@contentstack/cli-cm-clone) | Clone a stack to another stack | [Docs](https://www.contentstack.com/docs/headless-cms/cloning-a-stack) |
 | [`@contentstack/cli-cm-migrate-rte`](https://www.npmjs.com/package/@contentstack/cli-cm-migrate-rte) | Migrate HTML RTE entries to JSON RTE | [Docs](https://www.contentstack.com/docs/headless-cms/migrate-content-from-html-rte-to-json-rte) |
@@ -54,12 +54,12 @@ csdx plugins:install <plugin-name>
 
 | Plugin | Description | Docs |
 |--------|-------------|------|
-| [`@contentstack/apps-cli`](https://www.npmjs.com/package/@contentstack/apps-cli) | Build, deploy, and manage Contentstack apps | — |
-| [`contentstack-cli-tsgen`](https://www.npmjs.com/package/contentstack-cli-tsgen) | Generate TypeScript typings from a stack's content types | — |
-| [`contentstack-cli-content-type`](https://www.npmjs.com/package/contentstack-cli-content-type) | Retrieve and inspect content types in a stack | — |
-| [`@contentstack/cli-cm-regex-validate`](https://www.npmjs.com/package/@contentstack/cli-cm-regex-validate) | Validate regex properties on content type and global fields | — |
+| [`@contentstack/apps-cli`](https://www.npmjs.com/package/@contentstack/apps-cli) | Build, deploy, and manage Contentstack apps | [Docs](https://www.contentstack.com/docs/headless-cms/apps-cli-plugin) |
+| [`contentstack-cli-tsgen`](https://www.npmjs.com/package/contentstack-cli-tsgen) | Generate TypeScript typings from a stack's content types | [Docs](https://www.contentstack.com/docs/headless-cms/tsgen-plugin) |
+| [`contentstack-cli-content-type`](https://www.npmjs.com/package/contentstack-cli-content-type) | Retrieve and inspect content types in a stack | [Docs](https://www.contentstack.com/docs/headless-cms/cli-content-type-plugin) |
+| [`@contentstack/cli-cm-regex-validate`](https://www.npmjs.com/package/@contentstack/cli-cm-regex-validate) | Validate regex properties on content type and global fields | [Docs](https://www.contentstack.com/docs/headless-cms/cli-regex-validate-plugin) |
 | [`@contentstack/cli-external-migrate`](https://www.npmjs.com/package/@contentstack/cli-external-migrate) | Migrate content from an external source into Contentstack | — |
-| [`@contentstack/cli-cm-export-query`](https://www.npmjs.com/package/@contentstack/cli-cm-export-query) | Export stack content using query filters | — |
+| [`@contentstack/cli-cm-export-query`](https://www.npmjs.com/package/@contentstack/cli-cm-export-query) | Export stack content using query filters | [Docs](https://www.contentstack.com/docs/headless-cms/query-based-export) |
 
 ## License