@salesforce/plugin-deploy-retrieve 1.8.5-beta.5 → 1.8.6

package/messages/delete.tracking.md

@@ -1,39 +0,0 @@
-# resetSummary
-
-Reset local and remote source tracking.
-
-# resetDescription
-
-WARNING: This command deletes or overwrites all existing source tracking files. Use with extreme caution.
-
-Resets local and remote source tracking so that Salesforce CLI no longer registers differences between your local files and those in the org. When you next run 'project deploy preview', Salesforce CLI returns no results, even though conflicts might actually exist. Salesforce CLI then resumes tracking new source changes as usual.
-
-Use the --revision parameter to reset source tracking to a specific revision number of an org source member. To get the revision number, query the SourceMember Tooling API object with the 'data soql' command. For example:
-
-<%= config.bin %> data query --query "SELECT MemberName, MemberType, RevisionCounter FROM SourceMember" --use-tooling-api
-
-# deleteSummary
-
-Delete all local source tracking information.
-
-# deleteDescription
-
-WARNING: This command deletes or overwrites all existing source tracking files. Use with extreme caution.
-
-Deletes all local source tracking information. When you next run 'project deploy preview', Salesforce CLI displays all local and remote files as changed, and any files with the same name are listed as conflicts.
-
-# flags.no-prompt.summary
-
-Don't prompt for source tracking override confirmation.
-
-# flags.revision.summary
-
-SourceMember revision counter number to reset to.
-
-# promptMessage
-
-WARNING: This operation will modify all your local source tracking files. The operation can have unintended consequences on all the force:source commands. Are you sure you want to proceed?
-
-# conflictMsg
-
-We couldn't complete the operation due to conflicts. Verify that you want to keep the existing versions, then run the command again with the --forceoverwrite (-f) option.

package/messages/list.ignored.md

@@ -1,17 +0,0 @@
-# description
-
-check your local project package directories for forceignored files
-
-# examples
-
-- $ <%= config.bin %> <%= command.id %>
-
-- $ <%= config.bin %> <%= command.id %> --source-dir force-app
-
-# flags.source-dir
-
-file or directory of files that the command checks for foreceignored files
-
-# invalidSourceDir
-
-File or directory '%s' doesn't exist in your project. Specify one that exists and rerun the command.

package/messages/manifest.create.md

@@ -1,72 +0,0 @@
-# summary
-
-Create a project manifest that lists the metadata components you want to deploy or retrieve.
-
-# description
-
-Create a manifest from a list of metadata components (--metadata) or from one or more local directories that contain source files (--source-dir). You can specify either of these parameters, not both.
-
-Use --manifest-type to specify the type of manifest you want to create. The resulting manifest files have specific names, such as the standard package.xml or destructiveChanges.xml to delete metadata. Valid values for this parameter, and their respective file names, are:
-
-    * package : package.xml (default)
-    * pre : destructiveChangesPre.xml
-    * post : destructiveChangesPost.xml
-    * destroy : destructiveChanges.xml
-
-See https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy_deleting_files.htm for information about these destructive manifest files.
-
-Use --manifest-name to specify a custom name for the generated manifest if the pre-defined ones don’t suit your needs. You can specify either --manifest-type or --manifest-name, but not both.
-
-# examples
-
-- Create a manifest for deploying or retrieving all Apex classes:
-
-  $ <%= config.bin %> <%= command.id %> --metadata ApexClass
-
-- Create a manifest for deleting the specified Apex class:
-
-  $ <%= config.bin %> <%= command.id %> --metadata ApexClass:MyApexClass --manifest-type destroy
-
-- Create a manifest for deploying or retrieving all the metadata components in the specified local directory; name the file myNewManifest.xml:
-
-  $ <%= config.bin %> <%= command.id %> --source-dir force-app --manifest-name myNewManifest
-
-- Create a manifest from the metadata components in the specified org and include metadata in any unlocked packages:
-
-  $ <%= config.bin %> <%= command.id %> --from-org test@myorg.com --include-packages unlocked
-
-# flags.include-packages.summary
-
-Comma-separated list of package types (managed, unlocked) whose metadata is included in the manifest; by default, metadata in packages is ignored.
-
-# flags.from-org.summary
-
-Username or alias of the org that contains the metadata components from which to build a manifest.
-
-# flags.manifest-type.summary
-
-Type of manifest to create; the type determines the name of the created file.
-
-# flags.manifest-name.summary
-
-Name of a custom manifest file to create.
-
-# flags.output-dir.summary
-
-Directory to save the created manifest.
-
-# flags.source-dir.summary
-
-Comma-separated list of paths to the local source files to include in the manifest.
-
-# flags.metadata.summary
-
-Comma-separated list of names of metadata components to include in the manifest.
-
-# success
-
-successfully wrote %s
-
-# successOutputDir
-
-successfully wrote %s to %s

package/schemas/project-convert-mdapi.json

@@ -1,29 +0,0 @@
-{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "$ref": "#/definitions/ConvertMdapiJson",
-  "definitions": {
-    "ConvertMdapiJson": {
-      "type": "array",
-      "items": {
-        "type": "object",
-        "properties": {
-          "fullName": {
-            "type": "string"
-          },
-          "type": {
-            "type": "string"
-          },
-          "filePath": {
-            "type": "string"
-          },
-          "state": {
-            "type": "string",
-            "const": "Add"
-          }
-        },
-        "required": ["fullName", "type", "filePath", "state"],
-        "additionalProperties": false
-      }
-    }
-  }
-}