Move CLI include files to docs/core/tools/includes

docs/core/tools/dotnet-build-server.md

@@ -29,7 +29,7 @@ dotnet build-server -h|--help
 
 ## Options
 
-- [!INCLUDE [help](../../../includes/cli-help.md)]
+- [!INCLUDE [help](includes/cli-help.md)]
 
 - **`--msbuild`**
 

docs/core/tools/dotnet-build.md

@@ -44,7 +44,7 @@ For executable projects targeting .NET Core 3.0 and later, library dependencies
 
 Building requires the *project.assets.json* file, which lists the dependencies of your application. The file is created when [`dotnet restore`](dotnet-restore.md) is executed. Without the assets file in place, the tooling can't resolve reference assemblies, which results in errors.
 
-[!INCLUDE[dotnet restore note + options](~/includes/dotnet-restore-note-options.md)]
+[!INCLUDE[dotnet restore note + options](includes/dotnet-restore-note-options.md)]
 
 ### Executable or library output
 
@@ -69,17 +69,17 @@ In addition to its options, the `dotnet build` command accepts MSBuild options,
 
 Running `dotnet build` is equivalent to running `dotnet msbuild -restore`; however, the default verbosity of the output is different.
 
-[!INCLUDE [cli-advertising-manifests](../../../includes/cli-advertising-manifests.md)]
+[!INCLUDE [cli-advertising-manifests](includes/cli-advertising-manifests.md)]
 
 ## Arguments
 
-[!INCLUDE [arguments-project-solution-file](../../../includes/cli-arguments-project-solution-file.md)]
+[!INCLUDE [arguments-project-solution-file](includes/cli-arguments-project-solution-file.md)]
 
 ## Options
 
-- [!INCLUDE [arch](../../../includes/cli-arch.md)]
+- [!INCLUDE [arch](includes/cli-arch.md)]
 
-- [!INCLUDE [artifacts-path](../../../includes/cli-artifacts-path.md)]
+- [!INCLUDE [artifacts-path](includes/cli-artifacts-path.md)]
 
 - **`-bl|--binaryLogger:<FILE>`**
 
@@ -94,9 +94,9 @@ Running `dotnet build` is equivalent to running `dotnet msbuild -restore`; howev
   dotnet build -bl:build-log.binlog
   ```
 
-- [!INCLUDE [configuration](../../../includes/cli-configuration.md)]
+- [!INCLUDE [configuration](includes/cli-configuration.md)]
 
-- [!INCLUDE [disable-build-servers](../../../includes/cli-disable-build-servers.md)]
+- [!INCLUDE [disable-build-servers](includes/cli-disable-build-servers.md)]
 
 - **`-f|--framework <FRAMEWORK>`**
 
@@ -106,7 +106,7 @@ Running `dotnet build` is equivalent to running `dotnet msbuild -restore`; howev
 
   Forces all dependencies to be resolved even if the last restore was successful. Specifying this flag is the same as deleting the *project.assets.json* file.
 
-- [!INCLUDE [interactive](../../../includes/cli-interactive.md)]
+- [!INCLUDE [interactive](includes/cli-interactive.md)]
 
 - **`--no-dependencies`**
 
@@ -124,7 +124,7 @@ Running `dotnet build` is equivalent to running `dotnet msbuild -restore`; howev
 
   Doesn't display the startup banner or the copyright message.
 
-- [!INCLUDE [no-self-contained](../../../includes/cli-no-self-contained.md)]
+- [!INCLUDE [no-self-contained](includes/cli-no-self-contained.md)]
 
 - **`-o|--output <OUTPUT_DIRECTORY>`**
 
@@ -134,7 +134,7 @@ Running `dotnet build` is equivalent to running `dotnet msbuild -restore`; howev
 
     If you specify the `--output` option when running this command on a solution, the CLI will emit a warning (an error in 7.0.200) due to the unclear semantics of the output path. The `--output` option is disallowed because all outputs of all built projects would be copied into the specified directory, which isn't compatible with multi-targeted projects, as well as projects that have different versions of direct and transitive dependencies. For more information, see [Solution-level `--output` option no longer valid for build-related commands](../compatibility/sdk/7.0/solution-level-output-no-longer-valid.md).
 
-- [!INCLUDE [os](../../../includes/cli-os.md)]
+- [!INCLUDE [os](includes/cli-os.md)]
 
 - **`-p|--property:<PROPERTYNAME>=<VALUE>`**
 
@@ -149,23 +149,23 @@ Running `dotnet build` is equivalent to running `dotnet msbuild -restore`; howev
 
   Specifies the target runtime. For a list of Runtime Identifiers (RIDs), see the [RID catalog](../rid-catalog.md). If you use this option with .NET 6 SDK, use `--self-contained` or `--no-self-contained` also. If not specified, the default is to build for the current OS and architecture.
 
-- [!INCLUDE [self-contained](../../../includes/cli-self-contained.md)]
+- [!INCLUDE [self-contained](includes/cli-self-contained.md)]
 
 - **`--source <SOURCE>`**
 
   The URI of the NuGet package source to use during the restore operation.
 
-- [!INCLUDE [tl](../../../includes/cli-tl.md)]
+- [!INCLUDE [tl](includes/cli-tl.md)]
 
-- [!INCLUDE [use-current-runtime](../../../includes/cli-use-current-runtime.md)]
+- [!INCLUDE [use-current-runtime](includes/cli-use-current-runtime.md)]
 
-- [!INCLUDE [verbosity](../../../includes/cli-verbosity.md)]
+- [!INCLUDE [verbosity](includes/cli-verbosity.md)]
 
 - **`--version-suffix <VERSION_SUFFIX>`**
 
   Sets the value of the `$(VersionSuffix)` property to use when building the project. This only works if the `$(Version)` property isn't set. Then, `$(Version)` is set to the `$(VersionPrefix)` combined with the `$(VersionSuffix)`, separated by a dash.
 
-- [!INCLUDE [help](../../../includes/cli-help.md)]
+- [!INCLUDE [help](includes/cli-help.md)]
 
 ## Examples
 

docs/core/tools/dotnet-clean.md

@@ -30,21 +30,21 @@ The `dotnet clean` command cleans the output of the previous build. It's impleme
 
 ## Arguments
 
-[!INCLUDE [arguments-project-solution-file](../../../includes/cli-arguments-project-solution-file.md)]
+[!INCLUDE [arguments-project-solution-file](includes/cli-arguments-project-solution-file.md)]
 
 ## Options
 
-- [!INCLUDE [artifacts-path](../../../includes/cli-artifacts-path.md)]
+- [!INCLUDE [artifacts-path](includes/cli-artifacts-path.md)]
 
-- [!INCLUDE [configuration](../../../includes/cli-configuration-clean.md)]
+- [!INCLUDE [configuration](includes/cli-configuration-clean.md)]
 
 - **`-f|--framework <FRAMEWORK>`**
 
   The [framework](../../standard/frameworks.md) that was specified at build time. The framework must be defined in the [project file](../project-sdk/overview.md). If you specified the framework at build time, you must specify the framework when cleaning.
 
-- [!INCLUDE [help](../../../includes/cli-help.md)]
+- [!INCLUDE [help](includes/cli-help.md)]
 
-- [!INCLUDE [interactive](../../../includes/cli-interactive.md)]
+- [!INCLUDE [interactive](includes/cli-interactive.md)]
 
 - **`--nologo`**
 
@@ -62,9 +62,9 @@ The `dotnet clean` command cleans the output of the previous build. It's impleme
 
   Cleans the output folder of the specified runtime. This is used when a [self-contained deployment](../deploying/index.md#self-contained-deployment) was created.
 
-- [!INCLUDE [tl](../../../includes/cli-tl.md)]
+- [!INCLUDE [tl](includes/cli-tl.md)]
 
-- [!INCLUDE [verbosity](../../../includes/cli-verbosity-normal.md)]
+- [!INCLUDE [verbosity](includes/cli-verbosity-normal.md)]
 
 ## Examples
 

docs/core/tools/dotnet-format.md

@@ -85,9 +85,9 @@ None of the options below are required for the `dotnet format` command to succee
 
   Displays version information.
 
-- [!INCLUDE [verbosity](../../../includes/cli-verbosity.md)]
+- [!INCLUDE [verbosity](includes/cli-verbosity.md)]
 
-- [!INCLUDE [help](../../../includes/cli-help.md)]
+- [!INCLUDE [help](includes/cli-help.md)]
 
 ## Subcommands
 

docs/core/tools/dotnet-help.md

@@ -29,7 +29,7 @@ The `dotnet help` command opens up the reference page for more detailed informat
 
 ## Options
 
-- [!INCLUDE [help](../../../includes/cli-help.md)]
+- [!INCLUDE [help](includes/cli-help.md)]
 
 ## Examples
 

docs/core/tools/dotnet-new-details.md

@@ -36,13 +36,13 @@ If the package is installed locally or is found on the official NuGet website, i
   By default, `dotnet new details` uses the hierarchy of NuGet configuration files from the current directory to determine the NuGet source the package can be installed from. If `--nuget-source` is specified, the source is added to the list of sources to be checked.
   To check the configured sources for the current directory use [`dotnet nuget list source`](dotnet-nuget-list-source.md). For more information, see [Common NuGet Configurations](/nuget/consume-packages/configuring-nuget-behavior).
 
-- [!INCLUDE [interactive](../../../includes/cli-interactive.md)]
+- [!INCLUDE [interactive](includes/cli-interactive.md)]
 
 - **`-d|--diagnostics`**
 
   Enables diagnostic output.
 
-- [!INCLUDE [help](../../../includes/cli-help.md)]
+- [!INCLUDE [help](includes/cli-help.md)]
 
 ## Examples
 

docs/core/tools/dotnet-new-install.md

@@ -32,7 +32,7 @@ For example, if you install the template package using `dotnet new --install` in
 Starting with .NET SDK 6.0.100, installed template packages are available in later .NET SDK versions installed on your machine. A template package installed in .NET SDK 6.0.100 will also be available in .NET SDK 6.0.101, .NET SDK 6.0.200, and so on. However, these template packages won't be available in .NET SDK versions prior to .NET SDK 6.0.100. To use a template package installed in .NET SDK 6.0.100 or later in earlier .NET SDK versions, you need to install it using `dotnet new install` in that .NET SDK version.
 
 > [!NOTE]
-> [!INCLUDE [new syntax](../../../includes/dotnet-new-7-0-syntax.md)]
+> [!INCLUDE [new syntax](includes/dotnet-new-7-0-syntax.md)]
 >
 > Examples of old syntax:
 >
@@ -70,11 +70,11 @@ Starting with .NET SDK 6.0.100, installed template packages are available in lat
 
   Allows installing template packages from the specified sources even if they would override a template package from another source. Available since .NET SDK 7.0.100.
 
-- [!INCLUDE [help](../../../includes/cli-help.md)]
+- [!INCLUDE [help](includes/cli-help.md)]
 
-- [!INCLUDE [interactive](../../../includes/cli-interactive.md)]
+- [!INCLUDE [interactive](includes/cli-interactive.md)]
 
-- [!INCLUDE [verbosity](../../../includes/cli-verbosity.md)]
+- [!INCLUDE [verbosity](includes/cli-verbosity.md)]
 
 ## Examples
 

docs/core/tools/dotnet-new-list.md

@@ -27,7 +27,7 @@ The `dotnet new list` command lists available templates to use with `dotnet new`
 Starting with .NET SDK 7.0.100, the `list` command might not show all the templates installed on the machine. It takes the result of template constraints into account, and the templates that can't be used won't be shown. To force show all the templates, use the `--ignore-constraints` option.
 
 > [!NOTE]
-> [!INCLUDE [new syntax](../../../includes/dotnet-new-7-0-syntax.md)]
+> [!INCLUDE [new syntax](includes/dotnet-new-7-0-syntax.md)]
 >
 > Examples of the old syntax:
 >
@@ -75,7 +75,7 @@ Starting with .NET SDK 7.0.100, the `list` command might not show all the templa
 
   Enables diagnostic output. Available since .NET SDK 7.0.100.
 
-- [!INCLUDE [help](../../../includes/cli-help.md)]
+- [!INCLUDE [help](includes/cli-help.md)]
 
 - **`--ignore-constraints`**
 
@@ -104,7 +104,7 @@ Starting with .NET SDK 7.0.100, the `list` command might not show all the templa
 
   Filters templates based on template type. Predefined values are `project`, `item`, and `solution`.
 
-- [!INCLUDE [verbosity](../../../includes/cli-verbosity.md)]
+- [!INCLUDE [verbosity](includes/cli-verbosity.md)]
 
 ## Examples
 

docs/core/tools/dotnet-new-search.md

@@ -27,7 +27,7 @@ dotnet new search [<TEMPLATE_NAME>] [--author <AUTHOR>] [-lang|--language <langu
 The `dotnet new search` command searches for templates supported by `dotnet new` on NuGet.org. When the <TEMPLATE_NAME> is specified, searches for templates containing the specified name.
 
 > [!NOTE]
-> [!INCLUDE [new syntax](../../../includes/dotnet-new-7-0-syntax.md)]
+> [!INCLUDE [new syntax](includes/dotnet-new-7-0-syntax.md)]
 >
 > Examples of the old syntax:
 >
@@ -72,7 +72,7 @@ The `dotnet new search` command searches for templates supported by `dotnet new`
 
   Enables diagnostic output. Available since .NET SDK 7.0.100.
 
-- [!INCLUDE [help](../../../includes/cli-help.md)]
+- [!INCLUDE [help](includes/cli-help.md)]
 
 - **`-lang|--language <language>`**
 

docs/core/tools/dotnet-new-uninstall.md

@@ -23,7 +23,7 @@ dotnet new uninstall <PATH|NUGET_ID>
 The `dotnet new uninstall` command uninstalls a template package at the `PATH` or `NUGET_ID` provided. When the `<PATH|NUGET_ID>` value isn't specified, all currently installed template packages and their associated templates are displayed. When specifying `NUGET_ID`, don't include the version number.
 
 > [!NOTE]
-> [!INCLUDE [new syntax](../../../includes/dotnet-new-7-0-syntax.md)]
+> [!INCLUDE [new syntax](includes/dotnet-new-7-0-syntax.md)]
 >
 > Examples of the old syntax:
 >
@@ -51,9 +51,9 @@ The `dotnet new uninstall` command uninstalls a template package at the `PATH` o
 
   Enables diagnostic output. Available since .NET SDK 7.0.100.
 
-- [!INCLUDE [help](../../../includes/cli-help.md)]
+- [!INCLUDE [help](includes/cli-help.md)]
 
-- [!INCLUDE [verbosity](../../../includes/cli-verbosity.md)]
+- [!INCLUDE [verbosity](includes/cli-verbosity.md)]
 
 ## Examples
 

docs/core/tools/dotnet-new-update.md

@@ -27,7 +27,7 @@ The `dotnet new update` command updates installed template packages.
 The `dotnet new update` command with `--check-only` option checks for available updates for installed template packages without applying them.
 
 > [!NOTE]
-> [!INCLUDE [new syntax](../../../includes/dotnet-new-7-0-syntax.md)]
+> [!INCLUDE [new syntax](includes/dotnet-new-7-0-syntax.md)]
 >
 > Examples of the old syntax:
 >
@@ -47,7 +47,7 @@ The `dotnet new update` command with `--check-only` option checks for available
 
 ## Options
 
-- [!INCLUDE [interactive](../../../includes/cli-interactive.md)]
+- [!INCLUDE [interactive](includes/cli-interactive.md)]
 
 - **`--add-source|nuget-source <SOURCE>`**
 
@@ -62,9 +62,9 @@ The `dotnet new update` command with `--check-only` option checks for available
 
   Enables diagnostic output. Available since .NET SDK 7.0.100.
 
-- [!INCLUDE [help](../../../includes/cli-help.md)]
+- [!INCLUDE [help](includes/cli-help.md)]
 
-- [!INCLUDE [verbosity](../../../includes/cli-verbosity.md)]
+- [!INCLUDE [verbosity](includes/cli-verbosity.md)]
 
 ## Examples
 

docs/core/tools/dotnet-new.md

@@ -30,7 +30,7 @@ The `dotnet new` command creates a .NET project or other artifacts based on a te
 The command calls the [template engine](https://github.com/dotnet/templating) to create the artifacts on disk based on the specified template and options.
 
 > [!NOTE]
-> [!INCLUDE [new syntax](../../../includes/dotnet-new-7-0-syntax.md)]
+> [!INCLUDE [new syntax](includes/dotnet-new-7-0-syntax.md)]
 
 ### Tab completion
 
@@ -63,7 +63,7 @@ To activate tab completion for the .NET SDK, see [Enable tab completion](enable-
 
   Forces content to be generated even if it would change existing files. This is required when the template chosen would override existing files in the output directory.
 
-- [!INCLUDE [help](../../../includes/cli-help.md)]
+- [!INCLUDE [help](includes/cli-help.md)]
 
 - **`-lang|--language {C#|F#|VB}`**
 
@@ -98,7 +98,7 @@ To activate tab completion for the .NET SDK, see [Enable tab completion](enable-
 
   Enables diagnostic output. Available since .NET SDK 7.0.100.
 
-- [!INCLUDE [verbosity](../../../includes/cli-verbosity.md)]
+- [!INCLUDE [verbosity](includes/cli-verbosity.md)]
 
 ## Template options
 

docs/core/tools/dotnet-nuget-add-source.md

@@ -39,7 +39,7 @@ The `dotnet nuget add source` command adds a new package source to your NuGet co
 
 ## Options
 
-- [!INCLUDE [configfile](../../../includes/cli-configfile.md)]
+- [!INCLUDE [configfile](includes/cli-configfile.md)]
 
 - **`--allow-insecure-connections`**
 

docs/core/tools/dotnet-nuget-config-get.md

@@ -44,7 +44,7 @@ The `dotnet nuget config get` Gets the NuGet configuration settings that will be
 
   Specifies the directory to start from when listing configuration files. If not specified, the current directory is used.
 
-- [!INCLUDE [help](../../../includes/cli-help.md)]
+- [!INCLUDE [help](includes/cli-help.md)]
 
 ## Examples
 

docs/core/tools/dotnet-nuget-config-paths.md

@@ -30,7 +30,7 @@ The `dotnet nuget config paths` Lists the paths to all NuGet configuration files
 
   Specifies the directory to start from when listing configuration files. If not specified, the current directory is used.
 
-- [!INCLUDE [help](../../../includes/cli-help.md)]
+- [!INCLUDE [help](includes/cli-help.md)]
 
 ## Examples
 

docs/core/tools/dotnet-nuget-config-set.md

@@ -36,9 +36,9 @@ The `dotnet nuget config set` sets the values for NuGet configuration settings t
 
 ## Options
 
-- [!INCLUDE [configfile](../../../includes/cli-configfile.md)]
+- [!INCLUDE [configfile](includes/cli-configfile.md)]
 
-- [!INCLUDE [help](../../../includes/cli-help.md)]
+- [!INCLUDE [help](includes/cli-help.md)]
 
 ## Examples
 

docs/core/tools/dotnet-nuget-config-unset.md

@@ -32,9 +32,9 @@ The `dotnet nuget config unset` unsets the values for NuGet configuration settin
 
 ## Options
 
-- [!INCLUDE [configfile](../../../includes/cli-configfile.md)]
+- [!INCLUDE [configfile](includes/cli-configfile.md)]
 
-- [!INCLUDE [help](../../../includes/cli-help.md)]
+- [!INCLUDE [help](includes/cli-help.md)]
 
 ## Examples
 

docs/core/tools/dotnet-nuget-delete.md

@@ -42,9 +42,9 @@ The `dotnet nuget delete` command deletes or unlists a package from the server.
 
   Forces the application to run using an invariant, English-based culture.
 
-* [!INCLUDE [help](../../../includes/cli-help.md)]
+* [!INCLUDE [help](includes/cli-help.md)]
 
-* [!INCLUDE [interactive](../../../includes/cli-interactive.md)]
+* [!INCLUDE [interactive](includes/cli-interactive.md)]
 
 * **`-k|--api-key <API_KEY>`**