Skip to content

Commit a1d2880

Browse files
authored
Updating CodePush CLI (#3147)
* Updating CodePush CLI Remove code-push-standalone in favor of code-push * Update codepush-integration.md
1 parent 9cd6d28 commit a1d2880

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

content/integrations/codepush-integration.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -84,7 +84,7 @@ scripts:
8484
{{</notebox>}}
8585

8686

87-
7. In order to reveal the Deployment keys, run **code-push-standalone deployment ls YOUR_APP_NAME -k**
87+
7. In order to reveal the Deployment keys, run **code-push deployment ls YOUR_APP_NAME -k**
8888
8. By default, you get two Deployment channels: Staging and Production. You can add new ones, rename or delete them by running the following commands:
8989

9090
{{< highlight bash "style=paraiso-dark">}}
@@ -101,9 +101,9 @@ To Rename: code-push app rename <appName> <newAppName>
101101
To Delete: code-push app rm <appName>
102102
{{< /highlight >}}
103103

104-
10. If you need to patch a previous release, e.g. increase the rollout percentage, push a missed bug fix or similar, you can achieve it by running **code-push patch <appName> <deploymentName>**
104+
10. If you need to patch a previous release, e.g. increase the rollout percentage, push a missed bug fix or similar, you can achieve it by running `code-push patch <appName> <deploymentName>`
105105

106-
11. You cannot delete a deployed release, but you can roll back a release by running **code-push rollback <appName> <deploymentName>**
106+
11. You cannot delete a deployed release, but you can roll back a release by running `code-push rollback <appName> <deploymentName>`
107107

108108
12. After testing an update against a deployment channel, it is possible to promote it by running the following command:
109109

0 commit comments

Comments
 (0)