From cb8e46d27d0f705c64ab4fc5fe603ebe217b0ae5 Mon Sep 17 00:00:00 2001 From: Juliet Shackell <63259011+jshackell-sfdc@users.noreply.github.com> Date: Thu, 26 Sep 2024 10:06:57 -0700 Subject: [PATCH 1/2] fix: update link to MD api guide --- messages/promoteFlags.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/messages/promoteFlags.md b/messages/promoteFlags.md index 904c05a8..044d011e 100644 --- a/messages/promoteFlags.md +++ b/messages/promoteFlags.md @@ -42,7 +42,7 @@ Valid values are: - RunAllTestsInOrg — All tests in your org are run, including tests of managed packages. -If you don’t specify a test level, the default behavior depends on the contents of your deployment package. For more information, see [Running Tests in a Deployment](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy_running_tests.htm) in the "Metadata API Developer Guide". +If you don’t specify a test level, the default behavior depends on the contents of your deployment package. For more information, see the section "Running Tests in a Deployment" in the "Metadata API Developer Guide". (https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy_running_tests.htm) # promote.async.description From 7a418046c00e4dfca616e478cd6c3da3b2f3751a Mon Sep 17 00:00:00 2001 From: Juliet Shackell <63259011+jshackell-sfdc@users.noreply.github.com> Date: Thu, 26 Sep 2024 10:11:06 -0700 Subject: [PATCH 2/2] Update commonFlags.md While the code that gets the topic name of the command works when running --help, the code is shown literally in the CLI Reference. So I just hard-coded the command, which I think is fine. --- messages/commonFlags.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/messages/commonFlags.md b/messages/commonFlags.md index 32d438d1..d890f55b 100644 --- a/messages/commonFlags.md +++ b/messages/commonFlags.md @@ -8,7 +8,7 @@ Username or alias for the org where DevOps Center is installed. # flags.wait.description -If the command continues to run after the wait period, the CLI returns control of the terminal window to you and returns the job ID. To check the status of the operation, run "<%= config.bin %> <%= command.id.split(' ').slice(0, -1).join(' ') %> report". +If the command continues to run after the wait period, the CLI returns control of the terminal window to you and returns the job ID. To check the status of the operation, run "sf project deploy pipeline report". # flags.wait.summary